Net8 Administrator's Guide Release 8.1.5 A67440-01 |
|
A complete listing of all Net8 configuration parameters is provided for your reference. The following sections appear in this appendix:
The configuration files in a Net8 network consist of parameters which include keyword-value pairs. Keyword-value pairs are surrounded by parentheses:
parameter=(keyword=value)
Some keywords have other keyword-value pairs as their values:
(keyword= (keyword=value) (keyword=value) )
For example, the address portion of a local naming configuration file (TNSNAMES.ORA) might include the following lines:
(address= (protocol=tcp) (host=max) (port=1521) )
Set up configuration files so that indentation reflects what keyword is the parent or owner of other keyword-value pairs. This format is not required, but it does make the files much easier to read and understand.
Even if you do not choose to indent your files in this way, you must indent a wrapped line by at least one space, or it will be misread as a new parameter. The following layout is acceptable:
(address=(protocol=tcp) (host=max)(port=1521))
The following layout is not acceptable:
(address=(protocol=tcp) (host=max)(port=1521))
The following rules apply to the syntax of configuration files:
(address = (protocol=tcp) (host=martha) (port=1521) ) (address = (protocol=tcp) (port=1521) (host=martha) )
The network character set for keyword values consists of the following characters. Connect descriptors must be made up of single-byte characters.
A-Z, a-z
0-9
( ) < > / \
, . : ; ' "=- _
$ + * # & ! % ? @
Within this character set, the following symbols are reserved:
( )=\ " ' #
Reserved symbols are used as delimiters, not as part of a keyword or a value unless the keyword or value is quoted. Either single or double quotes can be used to enclose a value containing reserved symbols. To include a quote within a value that is surrounded by quotes, use different quote types. The backslash (\) is used as an escape character.
A specific example of the use of reserved symbols is a numeric DECnet object within an address. An OBJECT can be a name such as ABC or #123. These would be entered in the form:
or
Because the "#" sign is a reserved symbol, the character must be preceded by a backslash.
The following characters may be used within a connect descriptor, but not in a keyword or value:
The listener name, net service name, and Oracle Connection Manager names are limited to the following character set:
[a...z] [A...Z] [0...9] _
The first character must be an alphabetical character. In general, up to 64 characters is acceptable. A database service name must match the global database name defined by the database administrator, which consists of a database name (originally limited to eight characters), and the database domain. Net service names and global database names are not case sensitive.
When a connection is made, the client and the receiver of the request, such as a listener, Oracle Names server, or Oracle Connection Manager, are configured with identical protocol addresses. The purpose of the address is to identify the network address of a network object. The client uses this address to send the connection request to a particular network object location, and the recipient "listens" for requests on this address, and grants a connection based on its address information matching the client information. It is important to install the same protocols for the client and the connection recipient, as well as configure the same address.
Protocol address are comprised of two elements:
ADDRESS | |
---|---|
Purpose: |
Defines a protocol address. This parameter may be embedded under ADDRESS_LIST or DESCRIPTION. A DESCRIPTION is typically only used in a TNSNAMES.ORA or LISTENER.ORA file. Additional Information: Each protocol has its own required parameters needed in the address, as explained on "Configuring Protocol Addresses". |
Example: |
(address= (protocol=tcp) (host=sales-pc) (port=1521) ) |
The following parameters are available in a profile. Profiles are stored in a configuration file called SQLNET.ORA.SQLNET.ORA is located in $ORACLE_HOME/network/admin
on UNIX and ORACLE_HOME
\network\admin
on Windows platforms.
BEQUEATH_DETACH | |
---|---|
Purpose: |
Turn on/off signal handling in Net8 on UNIX systems. |
Default: |
NO which leaves signal handling on. |
Values: |
|
Example: |
bequeath_detach=yes |
DAEMON.TRACE_LEVEL | |
---|---|
Purpose: |
Turns tracing on/off to a certain specified level for the Oracle Enterprise Manager daemon. |
Default: |
OFF |
Values |
|
Example: |
daemon.trace_level=user |
DISABLE_OOB | |
---|---|
Purpose: |
Disables out of band breaks. |
Default: |
OFF |
Usage Notes: |
Disable out of band breaks if the underlying transport protocol does not support the feature. |
Example: |
disable_oob=off |
LOG_DIRECTORY_CLIENT | |
---|---|
Purpose: |
Controls the directory for where the log file is written. |
Default: |
Current directory where executable is started from. |
Example: |
log_directory_client=/oracle/network/log |
LOG_DIRECTORY_SERVER | |
---|---|
Purpose: |
Controls the directory for where the log file is written. |
Default: |
Current directory where executable is started from. |
Example: |
log_directory_server=/oracle/network/log |
LOG_FILE_CLIENT | |
---|---|
Purpose: |
Controls the log output file name for an Oracle client. |
Default: |
SQLNET.LOG |
Example: |
log_file_client=client |
LOG_FILE_SERVER | |
---|---|
Purpose: |
Controls the log output file name for an Oracle server. |
Default: |
SQLNET.LOG |
Example: |
log_file_server=svr.log |
NAMES.DCE.PREFIX | |
---|---|
Purpose: |
Specifies the DCE cell name (prefix) to use for name lookup. |
Default: |
|
Example: |
names.dce.prefix=/.:/subsys/oracle/names |
NAMES.NIS.META_MAP | |
---|---|
Purpose: |
Specifies the file to be used to map NIS attributes to an NIS mapname. |
Default: |
SQLNET.MAPS |
Example: |
names.nis.meta_map=sqlnet.maps |
NAMESCTL.INTERNAL_ENCRYPT_PASSWORD | |
---|---|
Purpose: |
If set to TRUE, NAMESCTL encrypts the password when it is sent to the Oracle Names server. If set to FALSE, NAMESCTL does not encrypt the password when it is sent to the Oracle Names server. This enables unencrypted passwords to be set in the NAMES.ORA file with the NAMES.PASSWORD parameter. |
Default: |
FALSE |
Values: |
TRUE | FALSE |
Example: |
namesctl.internal_encrypt_password=true |
NAMESCTL.INTERNAL_USE | |
---|---|
Purpose |
If set to TRUE, NAMESCTL enables a set of internal undocumented commands. All internal commands are preceded by an underscore in order to distinguish them as internal. |
NAMESCTL.SERVER_PASSWORD | |
---|---|
Purpose: |
Indicates the value that matches the configured password set in the NAMES.ORA file with the NAMES.PASSWORD parameter. This eliminates the need to enter the password with the SET PASSWORD command each time you use the NAMESCTL utility to perform secure options, such as STOP, RESTART and RELOAD. |
Example: |
namesctl.server_password=secret |
NAMESCTL.TRACE_LEVEL | |
---|---|
Purpose: |
Indicates the level at which the NAMESCTL program should be traced. |
Default: |
OFF |
Values: |
OFF, USER, ADMIN, SUPPORT |
Example: |
namesctl.trace_level=admin |
NAMESCTL.TRACE_FILE | |
---|---|
Purpose: |
Indicates the file in which the NAMESCTL trace output is placed. |
Default: |
NAMESCTL_PID.TRC |
Example: |
namesctl.trace_file=nmsctl |
OSS.SOURCE.LOCATION | |
---|---|
Purpose: |
Defines the method for retrieving encrypted private keys. |
Default: |
None |
Example: |
oss.source.location= (source= (method=oracle) (method_data= (sqlnet_address=oss))) |
SQLNET.AUTHENTICATION_KERBEROS5_SERVICE | |
---|---|
Purpose: |
Defines the name of the service used to obtain a Kerberos service ticket |
Default: |
None |
Example: |
sqlnet.authentication_kerberos5_service= oracle |
SQLNET.AUTHENTICATION_GSSAPI_SERVICE | |
---|---|
Purpose: |
Defines the CyberSAFE service principal |
SQLNET.CRYPTO_CHECKSUM_CLIENT | |
---|---|
Purpose: |
Specifies the desired checksum behavior when this client is connecting to a server |
Default: |
ACCEPTED |
Values: |
|
Example: |
sqlnet.crypto_checksum_client=accepted |
SQLNET.CRYPTO_CHECKSUM_SERVER | |
---|---|
Purpose: |
Specifies the desired checksum behavior when a client is connecting to this server |
Default: |
ACCEPTED |
Values: |
|
Example: |
sqlnet.crypto_checksum_server=accepted |
SQLNET.ENCRYPTION_CLIENT | |
---|---|
Purpose: |
Specifies the desired behavior when this client is connecting to a server |
Default: |
ACCEPTED |
Values: |
|
Example: |
sqlnet.encryption_client=accepted |
SQLNET.ENCRYPTION_SERVER | |
---|---|
Purpose: |
Specifies the desired behavior when a client is connecting to this server |
Default: |
ACCEPTED |
Values: |
|
Example: |
|
SQLNET.EXPIRE_TIME | |
---|---|
Purpose: |
Determines time interval to send a probe to verify the session is alive |
Default: |
None |
Minimum Value: |
0 minutes |
Recommended Value: |
10 minutes |
Example: |
sqlnet.expire_time=10 |
SQLNET.IDENTIX_FINGERPRINT_DATABASE | |
---|---|
Purpose: |
Specifies the service name or alias for the authentication fingerprint database |
Default: |
None |
Example: |
sqlnet.identix_fingerprint_database=fingrdb |
SQLNET.IDENTIX_FINGERPRINT_DATABASE_USER | |
---|---|
Purpose: |
Specifies the well known user name for the fingerprint database |
Default: |
None |
Example: |
sqlnet.identix_fingerprint_database_user=manager |
SQLNET.IDENTIX_FINGERPRINT_DATABASE_PASSWORD | |
---|---|
Purpose: |
Specifies the well known password for the fingerprint database |
Default: |
None |
Example: |
sqlnet.identix_fingerprint_database_password=password |
SQLNET.IDENTIX_FINGERPRINT_METHOD | |
---|---|
Purpose: |
Specifies the method name for the fingerprint database. The method name must be ORACLE |
Default: |
None |
Example: |
sqlnet.identix_fingerprint_method=oracle |
SQLNET.KERBEROS5_CLOCKSKEW | |
---|---|
Purpose: |
Specifies how many seconds can pass before a Kerberos credential is considered out of date. |
Default: |
300 |
Example: |
sqlnet.kerberos5_clockskew=1200 |
SQLNET.RADIUS_ALTERNATE_PORT | |
---|---|
Purpose: |
Listening port of the alternate RADIUS server. |
Default: |
1645 |
Example: |
sqlnet.radius_alternate_port= 1667 |
SQLNET.RADIUS_ALTERNATE_RETRIES | |
---|---|
Purpose: |
Times to resend |
Default: |
3 |
Example: |
sqlnet.radius_alternate_retries=4 |
SQLNET.RADIUS_AUTHENTICATION_TIMEOUT | |
---|---|
Purpose: |
Time to wait for response. |
Default: |
5 seconds |
Example: |
sqlnet.radius_authenetication_timeout= 10 |
SQLNET.RADIUS_AUTHENTICATION_PORT | |
---|---|
Purpose: |
Listening port of the primary RADIUS server. |
Default: |
1645 |
Example: |
sqlnet.radius_authenetication_port= 1667 |
SQLNET.RADIUS_AUTHENTICATION_RETRIES | |
---|---|
Purpose: |
Times to resend. |
Default: |
3 |
Example: |
sqlnet.radius_authenetication_retries=4 |
SQLNET.RADIUS_AUTHENTICATION_TIMEOUT | |
---|---|
Purpose: |
Time to wait for response. |
Default: |
5 seconds |
Example: |
sqlnet.radius_authenetication_timeout= 10 |
SQLNET.RADIUS_CHALLENGE_RESPONSE | |
---|---|
Purpose: |
Turns challenge response ON or OFF. |
Default: |
OFF |
Values: |
ON | OFF |
Example: |
sqlnet.radius_challenge_response=ON |
SSL_CIPHER_SUITES | |
---|---|
Purpose: |
Controls what combination of encryption and data integrity is used by SSL. |
Default: |
None |
Values: |
For further information about Cipher Suites, see the Oracle Advanced Security Administrator's Guide. |
Example: |
ssl_cipher_suite=(ssl_rsa_with_rc4_138_md5) |
SSL_VERSION | |
---|---|
Purpose: |
Forces the version of the SSL connection. Clients and servers must use a compatible version. |
Default: |
UNDETERMINED |
Values: |
UNDETERMINED | 2.0 | 3.0 |
Example: |
ssl_version=2.0 |
TNSPING.TRACE_DIRECTORY | |
---|---|
Purpose: |
Controls the destination directory of the trace file. |
Default: |
$ORACLE_HOME/network/trace |
Example: |
tnsping.trace_directory=/oracle/traces |
TNSPING.TRACE_LEVEL | |
---|---|
Purpose: |
Turns tracing on/off to a certain specified level. |
Default: |
OFF |
Values |
|
Example: |
tnsping.trace_level=admin |
TRACE_DIRECTORY_CLIENT | |
---|---|
Purpose: |
Controls the destination directory of the trace file. |
Default: |
$ORACLE_HOME/network/trace |
Example: |
trace_directory_client=/oracle/traces |
TRACE_DIRECTORY_SERVER | |
---|---|
Purpose: |
Controls the destination directory of the trace file. |
Default: |
$ORACLE_HOME/network/trace |
Example: |
trace_directory_server=/oracle/traces |
TRACE_FILE_CLIENT | |
---|---|
Purpose: |
Controls the name of the client trace file. |
Default: |
SQLNET.TRC |
Example: |
trace_file_client=clientsqlnet.trc |
TRACE_FILE_SERVER | |
---|---|
Purpose: |
Controls the name of the server trace file. |
Default: |
SVR_PID.TRC |
Example: |
trace_file_server=svrsqlnet.trc |
TRACE_LEVEL_CLIENT | |
---|---|
Purpose: |
Turns tracing on/off to a certain specified level. |
Default: |
OFF |
Values |
|
Example: |
trace_level_client=user |
TRACE_LEVEL_SERVER | |
---|---|
Purpose: |
Turns tracing on/off to a certain specified level. |
Default: |
OFF |
Values |
|
Example: |
trace_level_server=admin |
USE_DEDICATED_SERVER | |
---|---|
Purpose: |
Forces the listener to spawn a dedicated server process for sessions from this client. |
Default: |
OFF |
Values: |
|
Example: |
use_dedicated_server=on |
With the local naming method, net service names are added to the TNSNAMES.ORA file. TNSNAMES.ORA is located in $ORACLE_HOME/network/admin
on UNIX and ORACLE_HOME
\network\admin
on Windows platforms.
A net service name is an alias mapped to a database network address contained in a connect descriptor. A connect descriptor contains the location of the listener through a protocol address and the service name of the database to which to connect. Clients and servers that are clients of other servers use this net service name when making a connection with an application.
The basic syntax for a TNSNAMES.ORA file's is shown in Figure C-1. DESCRIPTION contains the connect descriptor, ADDRESS is the listener address, and CONNECT_DATA contains the database service name.
net_service_name= (description=(address= (
protocol_address_information))
(connect_data= (service_name=service_name) ) )
A TNSNAMES.ORA file may contain one or more connect descriptors. Each connect descriptor can contain one or more listener addresses. Shown below in Figure C-2 are two connect descriptors with multiple addresses. DESCRIPTION_LIST defines a list of connect descriptors.
net_service_name= (description_list= (description=(address= (
protocol_address_information))
(address= (
protocol_address_information))
(address= (
protocol_address_information))
(connect_data= (service_name=service_name) ) ) (description=(address= (
protocol_address_information))
(address= (
protocol_address_information))
(address= (
protocol_address_information))
(connect_data= (service_name=service_name) ) ) )
The TNSNAMES.ORA also supports multiple list of addresses, each with its own characteristics. In Figure C-3, two address lists are presented. The first address list features client load balancing and no connect-time failover, affecting only those listener ADDRESSes within the ADDRESS_LIST. The second address list features connect-time failover and no client load loading balance, affecting only those listener ADDRESSes within the ADDRESS_LIST. The client will first try either the first or second address at random, then try address three and four sequentially.
net_service_name= (description= (address_list= (load_balance=on) (failover=off)(address= (
protocol_address_information))
(address= (
protocol_address_information))
) (address_list= (load_balance=off) (failover=on)(address= (
protocol_address_information))
(address= (
protocol_address_information))
) (connect_data= (service_name=service_name) ) )
Prior to release 8.1, DESCRIPTION_LISTs were used for client load balancing of multiple listeners. While client load balancing is still on by default for DESCRIPTION_LISTs, client load balancing can also be explicitly specified for an ADDRESS_LIST or associated with a set of ADDRESSes or set DESCRIPTIONs. Shown in Figure C-4 is a comparison of a TNSNAMES.ORA prior to release 8.1 and for release 8.1, using client load balancing in an Oracle Parallel Sever environment:
When a client goes through an Oracle Connection Manager for a connection to a service, the first address (or set of address) is for a client connection to an Oracle Connection Manager and the second address (or set of addresses) is for an Oracle Connection Manager connection to a service using listener.
When the Oracle Connection Manager parameter SOURCE_ROUTE is set to YES, it instructs the client to go through all the addresses listed before connecting.
Shown in Figure C-5 is an example with multiple Oracle Connection Manager addresses:
sample1=(description= (source_route=yes) (address=(protocol=tcp)(host=host1)(port=1630)) # hop 1 (address_list= (failover=on) (load_balance=off) # hop 2 (address=(protocol=tcp)(host=host2a)(port=1630)) (address=(protocol=tcp)(host=host2b)(port=1630)) ) (address=(protocol=tcp)(host=host3)(port=1521)) # hop 3 ) (connect_data=(service_name=sales.acme.com)) )
In the example above:
(address=(protocol=tcp)(host=host1)(port=1630)
(address_list= (failover=on) (load_balance=off) # hop 2 (address=(protocol=tcp)(host=host2a)(port=1630)) (address=(protocol=tcp)(host=host2b)(port=1630))
(address=(protocol=tcp)(host=host3)(port=1521)) # hop 3
Shown in Figure C-6 is an example of client load balancing among two Oracle Connection Managers and two listener addresses:
sample2=(description= (load_balance=on) (failover=on) (address_list= (source_route=yes) (address=(protocol=tcp)(host=host1)(port=1630)) (address=(protocol=tcp)(host=host2)(port=1521)) ) (address_list= (source_route=yes) (address=(protocol=tcp)(host=host3)(port=1630)) (address=(protocol=tcp)(host=host4)(port=1521)) ) (connect_data=(service_name=sales.acme.com)) )
In the example above:
ADDRESS | |
---|---|
Purpose: |
Defines a listener protocol address. This parameter may be embedded under a ADDRESS_LIST or DESCRIPTION. Additional Information: See "Configuring Protocol Addresses" for descriptions of the correct parameters to use for each protocol. |
Example: |
net_service_name= (description= (address =...) (address =...) ) (connect_data=(service_name=sales.com)) |
FAILOVER | |
---|---|
Purpose: |
When set to ON, instructs Net8 at connect time to fail over to a different listener if the first listener fails. It determines how many addresses are tried. When set to OFF, instructs Net8 to try one address. This parameter must be embedded under a DESCRIPTION_LIST, DESCRIPTION or ADDRESS_LIST. Note: This feature will not work if the LISTENER.ORA is configured with static service configuration parameters. See "SID_LIST_listener_name Static Service Section" for further information about these parameters. Static configuration is required for Oracle8i release 8.0 or Oracle7 databases and Oracle Enterprise Manager. |
Default: |
ON for DESCRIPTION_LISTs, DESCRIPTIONs, and ADDRESS_LISTs. |
Values: |
ON | OFF | YES | NO | TRUE | FALSE |
Example: |
net_service_name= (description= (failover=on) (address =...) (address =...) ) (connect_data=(service_name=sales.com))) |
CONNECT_DATA offers the following parameters:
FAILOVER_MODE | |
---|---|
Purpose: |
Instructs Net8 to fail over to a different listener if the first listener fails during runtime. Depending upon the configuration, session or any SELECT statements which were in progress are automatically failed over. This parameter must be embedded under CONNECT_DATA.
This type of failover is called "Transparent Application Failover" and should not be confused with the "Connect-Time Failover" FAILOVER parameter. See |
Sub-Parameters |
FAILOVER_MODE supports the following sub-parameters:
|
Example: |
Shown below is an example of transparent application failover (FAILOVER_MODE) to a backup node called OPSHP2 during a failure of OPSHP1. Any SELECT statements in progress will be failed over. net_service_name= (description= Shown below is transparent application failover (FAILOVER_MODE) being used with connect-time failover (FAILOVER). A connection will be tried first to OPSHP1, then to OPSHP2. If, after a connection, the node fails, the application will try to failover to the OPSHP1, then OPSHP2, reserving any SELECT statements in progress. net_service_name= (description= (failover=on) |
INSTANCE_NAME | |
---|---|
Purpose: |
Identifies the database instance name to access. This parameter may be embedded under CONNECT_DATA. The instance name can be obtained from the INSTANCE_NAME parameter in the INITSID.ORA file. The INSTANCE_NAME is typically the system identifier (SID) entered during installation or database creation. Additional Information:"Configuring Protocol Addresses" for information on setting the instance name string. |
Example: |
net_service_name= (description = (address=...) (address=...) (connect_data= (service_name=sales.com) (instance_name=sales1)) |
SERVICE_NAME | |
---|---|
Purpose: |
Identifies the release 8.1 service to access. This parameter must be embedded under CONNECT_DATA. The SERVICE_NAME is typically set to the global database name, a name comprised of the database name and domain name, entered during installation or database creation. Additional Information: See "Setting Service Names and Instance Names" for information on setting the instance name. |
Example: |
net_service_name= (description = (address=...) (address=...) (connect_data= (service_name=sales.com) (instance_name=sales1)) |
The following items are available in the network listener configuration file (LISTENER.ORA).
LISTENER.ORA is located in $ORACLE_HOME/network/admin
on UNIX and ORACLE_HOME
\network\admin
on Windows NT.
The listener address section of the LISTENER.ORA defines the protocol address(es) of the listener.
DESCRIPTION | |
---|---|
Purpose: |
Defines a listener protocol address, as well as the presentation and session communication layers to use. Prior to this release, Net8 only supported connections that used the Two-Task Common (TTC) presentation layer and Transparent Network Substrate (TNS) Network session (NS) layer to establish client connections. In order for clients to connect to the Java option in the database, the presentation layer and session layer support have been expanded. For those clients wishing to connect to the Java option, the General Inter-Orb Protocol (GIOP) presentation layer is used with no session layer. This parameter may be embedded under a DESCRIPTION_LIST. It is not necessary to use DESCRIPTIONs if all the protocol addresses specified use TTC and NS. Additional Information: See "Configuring Java Option Connections" for configuration information. |
Example: |
listener_name = (description_list = (description = (address= (protocol=ipc) (key=extproc0)) ) (description = (protocol_stack = (presentation=giop) (session=raw)) (address= (protocol=tcp) (host=sales-pc) (port=2481)) ) |
ADDRESS | |
---|---|
Purpose: |
Defines a listener protocol address. This parameter may be embedded under a ADDRESS_LIST or DESCRIPTION. Additional Information: See "Configuring Protocol Addresses" for descriptions of the correct parameters to use for each protocol. |
Example: |
listener_name = (address= (protocol=ipc) (key=extproc0)) (address= (protocol=tcp) (host=sales-pc) (port=2481)) |
PROTOCOL_STACK | |
---|---|
Purpose: |
Prior to this release, Net8 only supported connections that used the Two-Task Common (TTC) presentation layer and Network Session (NS) layer to establish client connections. For those clients wishing to connect to the Java option, the General Inter-Orb Protocol (GIOP) presentation layer is used with no session layer. This parameter must be embedded under a DESCRIPTION. It is not necessary to use PROTOCOL_STACK if the protocol address(es) specified use TTC and NS. Additional Information: See "Configuring Java Option Connections" for further configuration information. |
Example: |
listener_name = (description_list = (description = (address= (protocol=ipc) (key=extproc0)) ) (description = (protocol_stack = (presentation=giop) (session=raw)) (address= (protocol=tcp) (host=sales-pc) (port=2481)) ) |
PRESENTATION | |
---|---|
Purpose: |
Identifies the presentation layer. |
Default: |
TTC |
Values: |
Typical Net8 clients use a presentation layer of Two-Task Common (TTC). IIOP clients require a presentation layer of GIOP. GIOP is an alias for either oracle.aurora.server.SGiopServer or oracle.aurora.server.GiopServer using TCP/IP or TCP/IP with SSL. Additional Information: See "Configuring Java Option Connections" for further configuration information. |
Example: |
listener_name = (description_list = (description = (address= (protocol=ipc) (key=extproc0)) ) (description = (protocol_stack = (presentation=giop) (session=raw)) (address= (protocol=tcp) (host=sales-pc) (port=2481)) ) |
SESSION | |
---|---|
Purpose: |
Identifies the session layer. |
Default: |
NS |
Values: |
IIOP clients require no session layer (RAW). Typical Net8 clients use a session layer of Transparent Network Substrate (TNS) Network Session (NS). |
Example: |
listener_name = (description_list = (description = (address= (protocol=ipc) (key=extproc0)) ) (description = (protocol_stack = (presentation=giop) (session=raw)) (address= (protocol=tcp) (host=sales-pc) (port=2481)) ) |
The SID_LIST section of the LISTENER.ORA defines the system identifier (SID) of the database served by the listener. This section is only valid for version 7.x and version 8.0 Oracle databases, as instance information is now automatically registered with the listener. Static configuration is also required for other services, such as external procedures and heterogeneous services, and some management tools, including Oracle Enterprise Manager.
CAUTION: Implementing connect-time failover does not allow use of static service configuration parameters in the LISTENER.ORA file. However, static configuration is required for Oracle8i release 8.0 or Oracle7 databases and Oracle Enterprise Manager. For further information about statically configuring the listener, see "Configuring a Listener with Service Information". See the Oracle8i Parallel Server Setup and Configuration Guide for instructions on setting up connect-time failover in an Oracle Enterprise environment. |
sid_list_listener_name= (sid_list= (sid_desc= (global_dbname=global_database_name) (sid_name=sid) (oracle_home=oracle_home) (prespawn_max=99) (prespawn_list= (prespawn_desc= (protocol=tcp) (pool_size=10) (timeout=2)) (prespawn_desc=...)) (sid_desc=...) )
SID_LIST contains the following parameters:
SID_LIST | |
---|---|
Purpose: |
Identifies a list of SID descriptions. |
Example: |
sid_list_listener_name= (sid_list= (sid_desc=...) (sid_desc=...) ) |
SID_DESC | |
---|---|
Purpose: |
Defines a SID. This parameter may be embedded under SID_LIST. |
Example: |
sid_list_listener_name= (sid_list= (sid_desc=...) (sid_desc=...) ) |
PRESPAWN_DESC | |
---|---|
Purpose: |
Defines the protocol on which the listener creates prespawned dedicated server processes, as well as characteristics of the prespawned dedicated server. Each protocol must have its own PRESPAWN_DESC description. This parameter must be embedded under PRESPAWN_LIST. Additional Information: See "Configuring Prestarted or Prespawned Dedicated Servers" for descriptions of PROTOCOL, POOL_SIZE, and TIMEOUT. |
Example: |
sid_list_listener_name= (sid_list= (sid_desc= (global_dbname=oracle.com) (sid_name=sid) (oracle_home=/usr/oracle) (prespawn_max=99) (prespawn_list= (prespawn_desc= (protocol=tcp) (pool_size=10) (timeout=2)) (prespawn_desc=...))) )) |
The following parameters control the behavior of the listener:
LOG_FILE_listener_name | |
---|---|
Purpose: |
Sets the name of the log file for the listener. |
Default: |
LISTENER.LOG |
Example: |
log_file_listener=list.log |
TRACE_FILE_listener_name | |
---|---|
Purpose: |
Sets the name of the trace file for the listener. |
Default: |
LISTENER.TRC |
Example: |
trace_file_listener=list.trc |
TRACE_LEVEL_listener_name | |
---|---|
Purpose: |
Turns tracing on/off to a certain specified level. |
Default: |
OFF |
Values |
|
Example: |
trace_level_listener=admin |
The following parameters are available in an Oracle Names configuration file (NAMES.ORA). NAMES.ORA is located in $ORACLE_HOME/network/admin
on UNIX and ORACLE_HOME
\network\admin
on Windows NT.
NAMES.ADDRESSES | |
---|---|
Purpose: |
Describes the address on which the Oracle Names server listens. Any valid ADDRESS or ADDRESS_LIST is allowed. Additional Information: See:
|
Default: |
names.addresses= (address=(protocol=tcp)(host=oranamesrvr0)(port=1575) |
NAMES.AUTHORITY_REQUIRED | |
---|---|
Purpose: |
Determines whether system queries require authoritative answers. |
Default: |
FALSE |
Example: |
names.authority_required=true |
NAMES.FORWARDING_AVAILABLE | |
---|---|
Purpose: |
The Oracle Names server forwards operations to foreign regions if set to ON. |
Default |
ON |
Values: |
ON | OFF |
Example: |
names.forwarding_available=off |
NAMES.FORWARDING_DESIRED | |
---|---|
Purpose: |
If set to TRUE, then this Oracle Names servers forwards queries. |
Default: |
TRUE |
Values: |
TRUE | FALSE |
Example: |
names.forwarding_desired=true |
NAMES.LOG_UNIQUE | |
---|---|
Purpose: |
If set to TRUE, then the log file name will be unique and not overwrite existing log files. |
Default: |
FALSE |
Values: |
TRUE | FALSE |
Example: |
names.log_unique=true |
NAMES.MAX_REFORWARDS | |
---|---|
Purpose: |
Specifies the maximum number of times the server attempts to forward an operation. |
Default: |
2 |
Minimum Value: |
1 |
Maximum Value: |
15 |
Example: |
names.max_reforwards=2 |
NAMES.NO_MODIFY_REQUESTS | |
---|---|
Purpose: |
If set to TRUE, the server refuses any operations which modify the data in its region. |
Default: |
FALSE |
Values: |
TRUE | FALSE |
Example: |
names.no_modify_requests=true |
NAMES.NO_REGION_DATABASE | |
---|---|
Purpose: |
If set to TRUE, the server does not look for a region database. |
Default: |
FALSE |
Example: |
names.no_region_database=true |
NAMES.PASSWORD | |
---|---|
Purpose: |
Sets the password for an Oracle Names server, so that certain sensitive operations, such as STOP, RESTART and RELOAD operations in NAMESCTL are secure. If this parameter is set with the Net8 Assistant, the password is encrypted. A clear-text password may be made manually. If the password is clear-text, ensure the NAMESCTL.INTERNAL_ENCRYPT_PASSWORD parameter is set in the SQLNET.ORA file is set to FALSE. |
Default: |
None |
Example: |
names.password=625926683431aa55 |
NAMES.TRACE_FILE | |
---|---|
Purpose: |
Indicates the name of the output file from a Oracle Names server trace session. The file name extension is always .TRC. |
Default: |
NAMES |
Example: |
names.trace_file=onames |
NAMES.TRACE_FUNC | |
---|---|
Purpose: |
Enables internal mechanism to control tracing by function name. |
Default: |
FALSE |
Example: |
names.trace_func=false |
NAMES.TRACE_LEVEL | |
---|---|
Purpose: |
Indicates the level at which the Oracle Names server is to be traced. |
Default: |
OFF |
Values |
|
Example: |
names.trace_level=admin |
The following parameters are available in an Oracle Connection Manager configuration file (CMAN.ORA). CMAN.ORA is located in $ORACLE_HOME/network/admin
on UNIX and ORACLE_HOME
\network\admin
on Windows NT.
CMAN | |
---|---|
Purpose: |
Specifies listening addresses for Oracle Connection Manager gateway process, CMGW. |
Default: |
cman=(address=(protocol=tcp)(host=local_host)(port=1630)) |
Syntax: |
cman= [(address_list= ] (address= ...) [(address= ...))] |
CMAN_ADMIN | |
---|---|
Purpose: |
Specifies listening addresses for Oracle Connection Manager administrative process, CMADMIN. |
Default: |
cman_admin=(address=(protocol=tcp)(host=anyhost)(port=1830)) |
Syntax: |
[(address_list= ] (address= ...) [(address= ...))] |
The following parameters in the PROTOCOL.ORA configuration file are applicable to Net8.
protocol.VALIDNODE_CHECKING | |
---|---|
Purpose: |
Restricts connection access of clients to destinations with enabling host privilege. |
Default: |
NO |
Values: |
YES | NO |
Example: |
tcp.validnode_checking=yes |
TCP.NODELAY | |
---|---|
Purpose: |
Specifies no delays in buffer flushing. |
Default: |
NO |
Values: |
YES | NO |
Example: |
tcp.nodelay=yes |