C
Configuration Parameters

This appendix provides complete listing of all Net8 configuration parameters. It contains the following sections:

Syntax Rules for Configuration Files

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))

Further Syntax Rules for Configuration Files

The following rules apply to the syntax of configuration files:

Any keyword in a configuration file that begins a parameter that includes one or more keyword-value pairs must be in the far left column of a line. If it is indented by one or more spaces, it is interpreted as a continuation of the previous line.
All characters must belong to the network character set (see the next section).
Keywords are not case sensitive. Values may be case sensitive, depending on the operating system and protocol.
Spaces around the "=" sign are optional in keyword-value pairs.
There is a hierarchy of keywords in that some keywords are always followed by others. At any level of the hierarchy, keywords can be listed in any order. For example, the following entries are equally valid:
```
(address=
   (protocol=tcp)
   (host=martha)
   (port=1521))

(address=
   (protocol=tcp)
   (port=1521)
   (host=martha))
```
Keywords cannot contain spaces. Values must not contain spaces unless enclosed within double quotes (") or single quotes (').
The maximum length of a connect descriptor is 4 kilobytes.
Comments can be included using the pound sign # at the beginning of a line. Anything following the sign to the end of the line is considered a comment.
If the keyword-value pair consists of a single word or a concatenation of words on either side of the equal sign, no parentheses are needed.

Network Character Set

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:

(OBJECT=ABC)

(OBJECT=\#123)

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:

Character Set

The listener name, net service name, and Oracle Names server 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.

Profile Parameters (sqlnet.ora)

The following parameters are available in a profile.

The sqlnet.ora file is located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows platforms, or in the directory specified by the TNS_ADMIN environment variable or registry value.

BEQUEATH_DETACH

Purpose:

Turns signal handling on or off for UNIX systems

Default:

NO which leaves signal handling on.

Values:

YES - Turns off signal handling

NO - Leaves signal handling on

Example:

bequeath_detach=yes

BEQUEATH_DETACH
Purpose:	Turns signal handling on or off for UNIX systems
Default:	NO which leaves signal handling on.
Values:	YES - Turns off signal handling NO - Leaves signal handling on
Example:	bequeath_detach=yes

DAEMON.TRACE_DIRECTORY

Purpose:

Specifies the destination directory of the Oracle Enterprise Manager daemon trace file

Default:

$ORACLE_HOME/network/trace on UNIX platforms and ORACLE_HOME/network/trace on Windows platforms

Example:

daemon.trace_directory=/oracle/traces

DAEMON.TRACE_DIRECTORY
Purpose:	Specifies the destination directory of the Oracle Enterprise Manager daemon trace file
Default:	`$ORACLE_HOME/network/trace` on UNIX platforms and `ORACLE_HOME``/network/trace` on Windows platforms
Example:	daemon.trace_directory=/oracle/traces

DAEMON.TRACE_LEVEL

Purpose:

Turns tracing on/off to a certain specified level for the Oracle Enterprise Manager daemon

Default:

OFF

Values

OFF - No trace output

USER - User trace information

ADMIN - Administration trace information

SUPPORT - WorldWide Customer Support trace information

Example:

daemon.trace_level=user

DAEMON.TRACE_LEVEL
Purpose:	Turns tracing on/off to a certain specified level for the Oracle Enterprise Manager daemon
Default:	OFF
Values	OFF - No trace output USER - User trace information ADMIN - Administration trace information SUPPORT - WorldWide Customer Support trace information
Example:	daemon.trace_level=user

DAEMON.TRACE_MASK

Purpose:

Specifies that only the Oracle Enterprise Manager daemon trace entries are logged into the trace file

Default:

$ORACLE_HOME/network/trace on UNIX platforms and ORACLE_HOME/network/trace on Windows platforms

Example:

daemon.trace_mask=(106)

DAEMON.TRACE_MASK
Purpose:	Specifies that only the Oracle Enterprise Manager daemon trace entries are logged into the trace file
Default:	`$ORACLE_HOME/network/trace` on UNIX platforms and `ORACLE_HOME``/network/trace` on Windows platforms
Example:	daemon.trace_mask=(106)

DISABLE_OOB

Purpose:

If turned OFF, enables Net8 to send and receive "break" messages using urgent data provided by the underlying protocol.
If turned ON, disables the ability to send and receive "break" messages using urgent data provided by the underlying protocol. Once enabled, this feature applies to all protocols used by this client.
See Also: Oracle operating-system documentation to determine if the protocols you are using support urgent data requests. TCP/IP is an example of a protocol that supports this feature.

Default:

OFF

Example:

disable_oob=oN

DISABLE_OOB
Purpose:	If turned OFF, enables Net8 to send and receive "break" messages using urgent data provided by the underlying protocol. If turned ON, disables the ability to send and receive "break" messages using urgent data provided by the underlying protocol. Once enabled, this feature applies to all protocols used by this client. See Also: Oracle operating-system documentation to determine if the protocols you are using support urgent data requests. TCP/IP is an example of a protocol that supports this feature.
Default:	OFF
Example:	disable_oob=oN

LOG_DIRECTORY_CLIENT

Purpose:

Specifies the destination directory for the client log file

Default:

Current directory from which the executable is started

Example:

log_directory_client=/oracle/network/log

LOG_DIRECTORY_CLIENT
Purpose:	Specifies the destination directory for the client log file
Default:	Current directory from which the executable is started
Example:	log_directory_client=/oracle/network/log

LOG_DIRECTORY_SERVER

Purpose:

Specifies the destination directory for the server log file

Default:

Current directory from which the executable is started

Example:

log_directory_server=/oracle/network/log

LOG_DIRECTORY_SERVER
Purpose:	Specifies the destination directory for the server log file
Default:	Current directory from which the executable is started
Example:	log_directory_server=/oracle/network/log

LOG_FILE_CLIENT

Purpose:

Specifies the name of the log file for the client

Default:

sqlnet.log

Example:

log_file_client=client

LOG_FILE_CLIENT
Purpose:	Specifies the name of the log file for the client
Default:	`sqlnet.log`
Example:	log_file_client=client

LOG_FILE_SERVER

Purpose:

Specifies the name of the log file for the server

Default:

sqlnet.log

Example:

log_file_server=svr.log

LOG_FILE_SERVER
Purpose:	Specifies the name of the log file for the server
Default:	`sqlnet.log`
Example:	log_file_server=svr.log

NAMES.DCE.PREFIX

Purpose:

Specifies the DCE cell name (prefix) to use for name lookupS

Default:

/.:/subsys/oracle/names

Example:

names.dce.prefix=/.:/subsys/oracle/names

NAMES.DCE.PREFIX
Purpose:	Specifies the DCE cell name (prefix) to use for name lookupS
Default:	`/.:/subsys/oracle/names`
Example:	names.dce.prefix=/.:/subsys/oracle/names

NAMES.DEFAULT_DOMAIN

Purpose:

Sets the domain from which the client most often looks up names resolution requests. When this parameter is set, the default domain name is automatically appended to any unqualified net service name or service name.
For example, if the default domain is set to us.acme.com, the connect string CONNECT scott/tiger@sales gets searched as sales.us.acme.com. If the connect string includes the domain extension, (such as CONNECT scott/tiger@sales.acme.com), the domain is not appended.

Default:

NULL

Example:

names.default_domain=com

NAMES.DEFAULT_DOMAIN
Purpose:	Sets the domain from which the client most often looks up names resolution requests. When this parameter is set, the default domain name is automatically appended to any unqualified net service name or service name. For example, if the default domain is set to `us.acme.com`, the connect string `CONNECT scott/tiger@sales` gets searched as `sales.us.acme.com`. If the connect string includes the domain extension, (such as `CONNECT scott/tiger@sales.acme.com`), the domain is not appended.
Default:	NULL
Example:	names.default_domain=com

NAMES.DIRECTORY_PATH

Purpose:

Specifies the order of the naming methods that used for client name resolution lookups

Default:

TNSNAMES, ONAMES, HOSTNAME

Values:

TNSNAMES

ONAMES

HOSTNAME

DCE

LDAP

NIS

NOVELL

Example:

names.directory_path=(tnsnames, onames)

NAMES.DIRECTORY_PATH
Purpose:	Specifies the order of the naming methods that used for client name resolution lookups
Default:	TNSNAMES, ONAMES, HOSTNAME
Values:	TNSNAMES ONAMES HOSTNAME DCE LDAP NIS NOVELL
Example:	names.directory_path=(tnsnames, onames)

NAMES.INITIAL_RETRY_TIMEOUT

Purpose:

Determines how long a client waits for a response from an Oracle Names server before reiterating the request to the next server in the preferred servers list

Default:

15

Minimum Value:

1

Maximum Value:

600

Example:

names.initial_retry_timeout=20

NAMES.INITIAL_RETRY_TIMEOUT
Purpose:	Determines how long a client waits for a response from an Oracle Names server before reiterating the request to the next server in the preferred servers list
Default:	15
Minimum Value:	1
Maximum Value:	600
Example:	names.initial_retry_timeout=20

NAMES.MAX_OPEN_CONNECTIONS

Purpose:

Determines how many connections an Oracle Names client can have open at one time

Default:

10

Minimum Value:

3

Maximum Value:

64

Example:

names.max_open_connections=3

NAMES.MAX_OPEN_CONNECTIONS
Purpose:	Determines how many connections an Oracle Names client can have open at one time
Default:	10
Minimum Value:	3
Maximum Value:	64
Example:	names.max_open_connections=3

NAMES.MESSAGE_POOL_START_SIZE

Purpose:

Determines the initial number of messages allocated in the client's message pool which are used for forwarded message requests

Default:

10

Minimum Value:

3

Maximum Value:

256

Example:

names.message_pool_start_size=10

NAMES.MESSAGE_POOL_START_SIZE
Purpose:	Determines the initial number of messages allocated in the client's message pool which are used for forwarded message requests
Default:	10
Minimum Value:	3
Maximum Value:	256
Example:	names.message_pool_start_size=10

NAMES.NIS.META_MAP

Purpose:

Specifies the map file to be used to map NIS attributes to an NIS mapname

Default:

sqlnet.maps

Example:

names.nis.meta_map=sqlnet.maps

NAMES.NIS.META_MAP
Purpose:	Specifies the map file to be used to map NIS attributes to an NIS mapname
Default:	`sqlnet.maps`
Example:	names.nis.meta_map=sqlnet.maps

NAMES.NDS.NAME.CONTEXT

Purpose:

Specifies the naming context in the NDS tree where the database object resides

Default:

None

Example:

cn=Payroll.o=Oracle

NAMES.NDS.NAME.CONTEXT
Purpose:	Specifies the naming context in the NDS tree where the database object resides
Default:	None
Example:	cn=Payroll.o=Oracle

NAMES.PREFERRED_SERVERS

Purpose:

Indicates the name, addresses, and order of Oracle Names servers that are used for a client's name requests

Default:

None

Example:

names.preferred_servers= (address_list= (address=(protocol=ipc)(key=n23)) (address=(protocol=tcp)(host-nineva)(key=1575)) (address=(protocol=tcp)(host=cicada)(key=1575)))

NAMES.PREFERRED_SERVERS
Purpose:	Indicates the name, addresses, and order of Oracle Names servers that are used for a client's name requests
Default:	None
Example:	names.preferred_servers= (address_list= (address=(protocol=ipc)(key=n23)) (address=(protocol=tcp)(host-nineva)(key=1575)) (address=(protocol=tcp)(host=cicada)(key=1575)))

NAMES.REQUEST_RETRIES

Purpose:

Specifies the number of times the client should try each Oracle Names server in the list of preferred Oracle Names servers before allowing the operation to fail

Default:

1

Minimum Value:

1

Maximum Value:

5

Example:

names.request_retries=5

NAMES.REQUEST_RETRIES
Purpose:	Specifies the number of times the client should try each Oracle Names server in the list of preferred Oracle Names servers before allowing the operation to fail
Default:	1
Minimum Value:	1
Maximum Value:	5
Example:	names.request_retries=5

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:

TRUE

Values:

TRUE | FALSE

Example:

namesctl.internal_encrypt_password=true

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:	TRUE
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.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.NO_INITIAL_SERVER

Purpose:

If set to TRUE, NAMESCTL suppresses any error messages when unable to connect to a default Oracle Names server.

Default:

FALSE

Values

TRUE | FALSE

Example:

namesctl.no_initial_server=true

NAMESCTL.NO_INITIAL_SERVER
Purpose:	If set to TRUE, NAMESCTL suppresses any error messages when unable to connect to a default Oracle Names server.
Default:	FALSE
Values	TRUE \| FALSE
Example:	namesctl.no_initial_server=true

NAMESCTL.NOCONFIRM

Purpose:

Indicates whether sensitive commands (STOP, RELOAD, RESTART) should be prompted with a confirmation when running the NAMESCTL utility

Default:

OFF

Values

ON | OFF

Example:

namesctl.noconfirm=on

NAMESCTL.NOCONFIRM
Purpose:	Indicates whether sensitive commands (STOP, RELOAD, RESTART) should be prompted with a confirmation when running the NAMESCTL utility
Default:	OFF
Values	ON \| OFF
Example:	namesctl.noconfirm=on

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.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

NAMESCTL.TRACE_DIRECTORY

Purpose:

Indicates the directory where trace output from the NAMESCTL utility is placed

Default:

$ORACLE_HOME/network/trace on UNIX and ORACLE_HOME/network/trace on Windows NT

Example:

namesctl.trace_directory=/oracle/trace

NAMESCTL.TRACE_UNIQUE

Purpose:

Indicates whether a process identifier is appended to the name of each trace file generated, so that several can co-exist

Default:

ON

Values:

ON | OFF

Example:

namesctl.trace_unique=on

OSS.SOURCE.MY_WALLET

Purpose:

Specifies the location of wallets. Wallets are certificates, keys and trustpoints processed by SSL
See Also: Oracle Advanced Security Administrator's Guide

Default:

None

Example:

oss.source.my_wallet= (source= (method=file) (method_data= (directory=/home/smalladi/oss)))

SQLNET.AUTHENTICATION_SERVICES

Purpose:

Enables one or more authentication services. If authentication has been installed, it is recommended that this parameter be set to either NONE or to one of the authentication methods.

Default:

None

Values:

Authentication Available with Net8:
NONE - No authentication methods are used. A valid user name and password can be used to access the database.
ALL - Enables all authentication methods to be used
BEQ - Uses the Bequeath protocol
NDS - Uses NDS authentication
NTS - Uses Windows NT native authentication
Authentication Available with Oracle Advanced Security:
KERBEROS5 - Uses Kerberos authentication
SECURID - Uses SecurID authentication
CYBERSAFE - Uses Cybersafe authentication
IDENTIX - Uses Identix authentication
RADIUS - Uses RADIUS authentication
DCEGSSAPI - Uses DCE GSSAPI authentication
See Also: Oracle Advanced Security Administrator's Guide

Example:

sqlnet.authentication_services=(beq, kerberos5, cybersafe)

SQLNET.AUTHENTICATION_KERBEROS5_SERVICE

Purpose:

Defines the name of the service used to obtain a Kerberos service ticket
See Also: Oracle Advanced Security Administrator's Guide

Default:

None

Example:

sqlnet.authentication_kerberos5_service= oracle

SQLNET.AUTHENTICATION_GSSAPI_SERVICE

Purpose:

Defines the CyberSAFE service principal
See Also: Oracle Advanced Security Administrator's Guide

SQLNET.CLIENT_REGISTRATION

Purpose:

Sets a unique identifier for this client machine. This identifier is passed to the listener with any connection request and is included in the Audit Trail. The identifier can be any alphanumeric string up to 128 characters long.

Default:

None

Example:

sqlnet.client_registration 1432

SQLNET.CRYPTO_CHECKSUM_CLIENT

Purpose:

Specifies the checksum behavior for the client
See Also: Oracle Advanced Security Administrator's Guide

Default:

ACCEPTED

Values:

ACCEPTED - Turn on the security service if the other side wants it.

REJECTED - Do not turn on the security service even if the other side wants it.

REQUESTED - Turn on the security service if the other side allows it.

REQUIRED - Turn on the security service or do not make the connection.

Example:

sqlnet.crypto_checksum_client=accepted

SQLNET.CRYPTO_CHECKSUM_SERVER

Purpose:

Specifies the checksum behavior for the server
See Also: Oracle Advanced Security Administrator's Guide

Default:

ACCEPTED

Values:

ACCEPTED - Turn on the security service if the other side wants it.

REJECTED - Do not turn on the security service even if the other side wants it.

REQUESTED - Turn on the security service if the other side allows it.

REQUIRED - Turn on the security service or do not make the connection.

Example:

sqlnet.crypto_checksum_server=accepted

SQLNET_CRYPTO_CHECKSUM_TYPE_CLIENT

Purpose:

Specifies a list of crypto-checksum algorithms this client is allowed to use
See Also: Oracle Advanced Security Administrator's Guide

Default:

MD5

Values:

MD5 - RSA Data Security's MD5 algorithm

Example:

sqlnet.crypto_checksum_types_client=(md5)

SQLNET_CRYPTO_CHECKSUM_TYPE_SERVER

Purpose:

Specifies a list of crypto-checksum algorithms this server is allowed to use
See Also: Oracle Advanced Security Administrator's Guide

Default:

MD5

Values:

MD5 - RSA Data Security's MD5 algorithm

Example:

sqlnet.crypto_checksum_types_server=(md5)

SQLNET.CRYPTO_SEED

Purpose:

Specifies the characters used when generating cryptographic keys. The more random the characters are, the stronger the keys are. The string should be 10-70 random characters. This is required for when encryption or checksumming are turned on. Encryption is turned on if the SQLNET.ENCRYPTION_CLIENT parameter is specified for the client and the SQLNET.ENCRYPTION_SERVER parameter is specified for the server; checksumming is turned on if the SQLNET.CRYPTO_CHECKSUM_CLIENT parameter is specified for the client and the SQLNET.CRYPTO_CHECKSUM_SERVER parameter is specified for the server.
See Also: Oracle Advanced Security Administrator's Guide

Default:

qwertyuiopasdfghjkl;zxcvbnm,.s1

Example:

sqlnet.crypto_seed="qwertyuiopasdfghjkl;zxcvbnm,.s1"

SQLNET.ENCRYPTION_CLIENT

Purpose:

Turns encryption on for the client
See Also: Oracle Advanced Security Administrator's Guide

Default:

ACCEPTED

Values:

ACCEPTED - Turn on the security service if the other side wants it.

REJECTED - Do not turn on the security service even if the other side wants it.

REQUESTED - Turn on the security service if the other side allows it.

REQUIRED - Turn on the security service or do not make the connection.

Example:

sqlnet.encryption_client=accepted

SQLNET.ENCRYPTION_SERVER

Purpose:

Turns encryption on for the client
See Also: Oracle Advanced Security Administrator's Guide

Default:

ACCEPTED

Values:

ACCEPTED - Turn on the security service if the other side wants it.

REJECTED - Do not turn on the security service even if the other side wants it.

REQUESTED - Turn on the security service if the other side allows it.

REQUIRED - Turn on the security service or do not make the connection.

Example:

sqlnet.encryption_server=accepted

SQLNET.ENCRYPTION_TYPES_CLIENT

Purpose:

Specifies a list of encryption algorithms this client is allowed to use
See Also: Oracle Advanced Security Administrator's Guide

Default:

All algorithms are used if none are specified.

Values:

One or more of the following:
RC4_40 - This is RSA RC4 (40-bit key size)
RC4_56 - This is RSA RC4 (56-bit key size)
RC4_128 - This is RSA RC4 (128-bit key size)
DES - This is Standard DES (56-bit key size)
DES40 - This is DES40 (40-bit key size)

Example:

sqlnet.encryption_types_client=(rc4_40)

SQLNET.ENCRYPTION_TYPES_SERVER

Purpose:

Specifies a list of encryption algorithms this server is allowed to use when acting as a server
See Also: Oracle Advanced Security Administrator's Guide

Default:

All algorithms are used if none are specified.

Values:

RC4_40 - This is RSA RC4 (40-bit key size)
RC4_56 - This is RSA RC4 (56-bit key size)
RC4_128 - This is RSA RC4 (128-bit key size)
DES - This is Standard DES (56-bit key size)
DES40 - This is DES40 (40-bit key size)

Example:

sqlnet.encryption_types_server=(rc4_40, des, ...)

SQLNET.EXPIRE_TIME

Purpose:

Determines time interval to send a probe to verify the session is alive
See Also: Oracle Advanced Security Administrator's Guide

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
See Also: Oracle Advanced Security Administrator's Guide

Default:

None

Example:

sqlnet.identix_fingerprint_database=fingrdb

SQLNET.IDENTIX_FINGERPRINT_DATABASE_USER

Purpose:

Specifies the well-known user name for the fingerprint database
See Also: Oracle Advanced Security Administrator's Guide

Default:

None

Example:

sqlnet.identix_fingerprint_database_user=manager

SQLNET.IDENTIX_FINGERPRINT_DATABASE_PASSWORD

Purpose:

Specifies the well-known password for the fingerprint database
See Also: Oracle Advanced Security Administrator's Guide

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.
See Also: Oracle Advanced Security Administrator's Guide

Default:

None

Example:

sqlnet.identix_fingerprint_method=oracle

SQLNET.KERBEROS5_CC_NAME

Purpose:

Specifies the complete path name to the Kerberos credentials cache file
See Also: Oracle Advanced Security Administrator's Guide

Default:

/usr/tmp/krbcache on UNIX and c:\tmp\krbcache on Windows platforms

Example:

sqlnet.kerberos5_cc_name= /usr/tmp/krbcache

SQLNET.KERBEROS5_CLOCKSKEW

Purpose:

Specifies how many seconds can pass before a Kerberos credential is considered out of date
See Also: Oracle Advanced Security Administrator's Guide

Default:

300

Example:

sqlnet.kerberos5_clockskew=1200

SQLNET.KERBEROS5_CONF

Purpose:

Specifies the complete path name to the Kerberos configuration file, which contains the realm for the default KDC and maps realms to KDC hosts
See Also: Oracle Advanced Security Administrator's Guide

Default:

/krb5/krb.conf on UNIX and c:\krb5\krb.conf on Windows platforms

Example:

sqlnet.kerberos5_conf=/krb5/krb.conf

SQLNET.KERBEROS5_KEYTAB

Purpose:

Specifies the complete path name to the Kerberos principal/secret key mapping file, which is used to extract keys and decrypt incoming authentication information
See Also: Oracle Advanced Security Administrator's Guide

Default:

/etc/v5srvtab on UNIX and c:\krb5\v5srvtab on Windows platforms

Example:

sqlnet.kerberos5_keytab=/etc/v5srvtab

SQLNET.KERBEROS5_REALMS

Purpose:

Specifies the complete path name to the Kerberos realm translation file, which provides a mapping from a host name or domain name to a realm
See Also: Oracle Advanced Security Administrator's Guide

Default:

/krb5/krb.realms on UNIX and c:\krb5\krb.realms on Windows platforms

Example:

sqlnet.kerberos5_realms= /krb5/krb.realms

SQLNET.RADIUS_ALTERNATE

Purpose:

Specifies an alternate RADIUS server used in case the primary server is unavailable. The value can be either the IP address or host name of the server
See Also: Oracle Advanced Security Administrator's Guide

Default:

None

Example:

sqlnet.radius_alternate=radius2

SQLNET.RADIUS_ALTERNATE_PORT

Purpose:

Listening port of the alternate RADIUS server
See Also: Oracle Advanced Security Administrator's Guide

Default:

1645

Example:

sqlnet.radius_alternate_port= 1667

SQLNET.RADIUS_ALTERNATE_RETRIES

Purpose:

Specifies the number of times the Oracle Server should resend messages to the alternate RADIUS server
See Also: Oracle Advanced Security Administrator's Guide

Default:

3

Example:

sqlnet.radius_alternate_retries=4

SQLNET.RADIUS_AUTHENTICATION

Purpose:

Specifies the location of the primary RADIUS server, either by its host name or IP address
See Also: Oracle Advanced Security Administrator's Guide

Default:

local host

Example:

sqlnet.radius_authenetication= officeacct

SQLNET.RADIUS_AUTHENTICATION_INTERFACE

Purpose:

Specifies the class containing the user interface used to interact with the user
See Also: Oracle Advanced Security Administrator's Guide

Default:

DefaultRadiusInterface

Example:

sqlnet.radius_authenetication_interface=

SQLNET.RADIUS_AUTHENTICATION_PORT

Purpose:

Listening port of the primary RADIUS server
See Also: Oracle Advanced Security Administrator's Guide

Default:

1645

Example:

sqlnet.radius_authenetication_port= 1667

SQLNET.RADIUS_AUTHENTICATION_RETRIES

Purpose:

Specifies the number of times the Oracle Server should resend messages to the primary RADIUS server
See Also: Oracle Advanced Security Administrator's Guide

Default:

3

Example:

sqlnet.radius_authenetication_retries=4

SQLNET.RADIUS_AUTHENTICATION_TIMEOUT

Purpose:

Specifies the number of seconds the Oracle Server should wait for a response from the primary RADIUS server
See Also: Oracle Advanced Security Administrator's Guide

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

SQLNET.RADIUS_SECRET

Purpose:

Specifies the location of the RADIUS secret key
See Also: Oracle Advanced Security Administrator's Guide

Default:

$ORACLE_HOME/network/security/radius.key on UNIX and ORACLE_HOME/network/security/radius.key on Windows NT

Example:

sqlnet.radius_secret= oracle/bin/admin/radiuskey

SQLNET.RADIUS_SEND_ACCOUNTING

Purpose:

Turns accounting ON and OFF. If enabled, packets are sent to the active RADIUS server at listening port plus one. The default port is 1646
See Also: Oracle Advanced Security Administrator's Guide

Default:

OFF

Values:

ON | OFF

Example:

sqlnet.radius_send_accounting=ON

SSL_CLIENT_AUTHENTICATION

Purpose:

Specifies whether or not a client--in addition to the server--is authenticated using SSL
See Also: Oracle Advanced Security Administrator's Guide

Default:

TRUE

Values:

TRUE | FALSE

Example:

ssl_cipher_suite=(ssl_dh_dss_with_des_cdc_sha)

SSL_CIPHER_SUITES

Purpose:

Controls what combination of encryption and data integrity is used by SSL
See Also: Oracle Advanced Security Administrator's Guide

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.
See Also: Oracle Advanced Security Administrator's Guide

Default:

UNDETERMINED

Values:

UNDETERMINED | 2.0 | 3.0

Example:

ssl_version=2.0

TNSPING.TRACE_DIRECTORY

Purpose:

Specifies the destination directory for the TNSPING utility trace file

Default:

$ORACLE_HOME/network/trace

Example:

tnsping.trace_directory=/oracle/traces

TNSPING.TRACE_LEVEL

Purpose:

Turns tracing on/off at specified level for the TNSPING utility

Default:

OFF

Values

OFF - No trace output

USER - User-induced error conditions trace information

ADMIN - Administration trace information

SUPPORT - WorldWide Customer Support trace information

Example:

tnsping.trace_level=admin

TRACE_DIRECTORY_CLIENT

Purpose:

Specifies the destination directory for the client trace file

Default:

$ORACLE_HOME/network/trace

Example:

trace_directory_client=/oracle/traces

TRACE_DIRECTORY_SERVER

Purpose:

Specifies the destination directory for the client trace file

Default:

$ORACLE_HOME/network/trace

Example:

trace_directory_server=/oracle/traces

TRACE_FILE_CLIENT

Purpose:

Specifies the name of the client trace file

Default:

sqlnet.trc

Example:

trace_file_client=clientsqlnet.trc

TRACE_FILE_SERVER

Purpose:

Specifies the name of the server trace file

Default:

svr_pid.trc

Example:

trace_file_server=svrsqlnet.trc

TRACE_FILELEN_CLIENT

Purpose:

Specifies the size of the client trace files in kilobytes (KB). When the size is met, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_listener_name parameter.

Example:

trace_filelen_client=100

TRACE_FILELEN_SERVER

Purpose:

Specifies the size of the server trace files in kilobytes (KB). When the size is met, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_listener_name parameter.

Example:

trace_filelen_server=100

TRACE_FILENO_CLIENT

Purpose:

Specifies the number of trace files for client tracing. When this parameter is set along with the TRACE_FILELEN_listener_name parameter, trace files are used in a cyclical fashion. The first file is filled first, then the second file, and so on. When the last file has been filled, the first file is re-used, and so on.
The trace file names are distinguished from one another by their sequence number. For example, if the default trace file of svr_pid.trc is used, and this parameter is set to 3, the trace files would be named svr1_pid.trc, svr2_pid.trc and svr3_pid.trc.
In addition, trace events in the trace files are preceded by the sequence number of the file.

Default:

None

Example:

trace_fileno_server=3

TRACE_FILENO_SERVER

Purpose:

Specifies the number of trace files for server tracing. When this parameter is set along with the TRACE_FILELEN_listener_name parameter, trace files are used in a cyclical fashion. The first file is filled first, then the second file, and so on. When the last file has been filled, the first file is re-used, and so on.
The trace file names are distinguished from one another by their sequence number. For example, if the default trace file of svr_pid.trc is used, and this parameter is set to 3, the trace files would be named svr1_pid.trc, svr2_pid.trc and svr3_pid.trc.
In addition, trace events in the trace files are preceded by the sequence number of the file.

Default:

None

Example:

trace_fileno_server=3

TRACE_LEVEL_CLIENT

Purpose:

Turns tracing on or off on the client at a specified level

Default:

OFF

Values

OFF - No trace output

USER - User trace information

ADMIN - Administration trace information

SUPPORT - WorldWide Customer Support trace information

Example:

trace_level_client=user

TRACE_LEVEL_SERVER

Purpose:

Turns tracing on or off on the server at a specified level

Default:

OFF

Values

OFF - No trace output

USER - User trace information

ADMIN - Administration trace information

SUPPORT - WorldWide Customer Support trace information

Example:

trace_level_server=admin

TRACE_TIMESTAMP_CLIENT

Purpose:

Adds a timestamp in form of dd-month-yyyy hh:mm:ss to a trace event in the client trace file, which has a default name of sqlnet.trc

Default:

OFF

Values

ON or TRUE | OFF or FALSE

Example:

trace_timestamp_server=true

TRACE_TIMESTAMP_SERVER

Purpose:

Adds a timestamp in form of dd-month-yy hh:mm:ss to a trace event in the sever trace file, which has a default name of svr_pid.trc

Default:

OFF

Values

ON or TRUE | OFF or FALSE

Example:

trace_timestamp_server=true

TRACE_UNIQUE_CLIENT

Purpose:

Determines whether or not a unique trace file is created for each client trace file. If the value is set to ON, a process identifier is appended to the name of each trace file, so that several files named sqlnetpid.trc. can coexist. If the value is set to OFF, when a new trace file is created for a client, it overwrites the existing file.

Default:

ON

Example:

trace_unique_client=on

USE_CMAN

Purpose:

If set to TRUE, instructs the client to use a connect descriptor that contains an address list with a first address for Oracle Connection Manager location and a second address for the listener location. This way, the client is routed to an Oracle Connection Manager.
The following example shows two address lists. While the first address list routes the client to an Oracle Connection Manager, the second address list routes the client directly to a listener.
sales= (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= (address=(protocol=tcp)(host=host3)(port=1521))) (connect_data=(service_name=sales.us.acme.com)))

Without USE_CMAN=TRUE, the client picks one of the address lists at random and fails over to the other address list if the chosen ADDRESS_LIST fails. With USE_CMAN=TRUE, the client always uses the first address list.
If no Oracle Connection Manager addresses are available, connections are routed through any available listener address.
Note: If you are using Oracle Connection Manager with Oracle Names, this option must be set on clients and Oracle Names servers.

Default:

FALSE

Values:

TRUE | FALSE

Example:

use_cman=true

USE_DEDICATED_SERVER

Purpose:

If set to ON, (SERVER=DEDICATED) is automatically appended to a connect descriptor's connect data.This way, connections from this client use dedicated servers, even if MTS is configured.
Adds (SERVER=DEDICATED) to the CONNECT_DATA section of the connect descriptors the client uses. This parameter overrides any current value SERVER parameter.

Default:

OFF

Values:

ON - Spawns dedicated server processes

OFF - Hands off request to existing server processes

Example:

use_dedicated_server=on

Local Naming Parameters (tnsnames.ora)

With the local naming method, net service names are added to the tnsnames.ora file. The tnsnames.ora file is located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows platforms, or in the directory specified by the TNS_ADMIN environment variable or registry value.

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.

General Syntax

The basic syntax for a tnsnames.ora file is shown in Example C-1. DESCRIPTION contains the connect descriptor, ADDRESS contains the listener address, and CONNECT_DATA contains the database service identification information.

Example C-1 General Syntax of tnsnames.ora

net_service_name= 
 (description= 
   (address= (protocol_address_information))
   (connect_data= 
     (service_name=service_name)))

Multiple Descriptions

A tnsnames.ora file can contain net service names with one or more connect descriptors. Each connect descriptor can contain one or more listener addresses. Example C-2 shows two connect descriptors with multiple addresses. DESCRIPTION_LIST defines a list of connect descriptors.

Note:
The Net8 Assistant does not support multiple connect descriptors in a net service name.

Example C-2 Multiple Descriptions in tnsnames.ora

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))))

Multiple Address Lists

The tnsnames.ora file also supports connect descriptors with multiple lists of addresses, each with its own characteristics. In Example 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 first tries either the first or second address at random, then tries addresses three and four sequentially.

Note:
The Net8 Assistant only supports the creation of one address list in a connect descriptor.

Example C-3 Multiple Address Lists in tnsnames.ora

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)))

Note:
Address lists do not have to be embedded in an ADDRESS_LIST if there is only one list, as was the case prior to release 8.1.

Changed Functionality of Client Load Balancing and DESCRIPTION_LISTs

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 of DESCRIPTIONs. Shown in Example C-4 is a comparison of a tnsnames.ora file prior to release 8.1 and for release 8.1, using client load balancing in an Oracle Parallel Sever environment:

Example C-4 Client Load Balancing for Release 8.1 and Prior to Release 8.1

Client Load Balancing Prior to Release 8.1
The following example shows a release 8.0 tnsnames.ora file with net service names of op, op1, and op2.
op allows a client to randomly choose one of the two instances. op1 and op2 allow a client to connect to a specific Oracle Parallel Server instance.
op= (description_list= (description= (address= (protocol=tcp) (host=opsnt1) (port=1521)) (connect_data=(sid=op1))) (description= (address= (protocol=tcp) (host=opsnt2) (port=1521)) (connect_data=(sid=op2)))) op1= (description= (address= (protocol=tcp) (host=opsnt1) (port=1521)) (connect_data=(sid=op1))) op2= (description= (address= (protocol=tcp) (host=opsnt1) (port=1521)) (connect_data=(sid=op2)))

Client Load Balancing in Release 8.1
The following example shows a release 8.1 tnsnames.ora file with net service names of op, op1 and op2.
op allows a client to randomly to connect to database service op.com and choose one of the two instances using multiple ADDRESSes rather than multiple DESCRIPTIONs. op1 and op2 allow a client to connect to a specific Oracle Parallel Server instance.
op= (description= (load_balance=on) (address= (protocol=tcp) (host=opsnt1) (port=1521)) (address= (protocol=tcp) (host=opsnt2) (port=1521)) (connect_data= (service_name=op.com))) op1= (description= (address= (protocol=tcp) (host=opsnt1) (port=1521)) (connect_data= (service_name=op) (instance_name=op1))) op2= (description= (address= (protocol=tcp) (host=opsnt2) (port=1521)) (connect_data= (service_name=op) (instance_name=op2)))

Examples

When a client goes through an Oracle Connection Manager for a connection to a service, the first address (or set of addresses) 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 Example C-5 is an example with multiple Oracle Connection Manager addresses:

Example C-5 Multiple Oracle Connection Manager Addresses tnsnames.ora

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.us.acme.com)))

In Example C-5:

The client is instructed to connect to an address of the first Oracle Connection Manager, as indicated by:
```
(address=(protocol=tcp)(host=host1)(port=1630))
```
The first Oracle Connection Manager then connects to another Oracle Connection Manager by first trying the address of one Oracle Connection Manager. If the first address fails, it tries the second address. This is indicated by:
```
(address_list=  
  (failover=on) 
  (load_balance=off)
  (address=(protocol=tcp)(host=host2a)(port=1630)) 
  (address=(protocol=tcp)(host=host2b)(port=1630)) 
```
The Oracle Connection Manager then connects to the database service using the following listener address:
```
(address=(protocol=tcp)(host=host3)(port=1521)) 
```

Shown in Example C-6 is an example of client load balancing among two Oracle Connection Managers and two listener addresses:

Example C-6 Client Load Balancing in tnsnames.ora

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.us.acme.com)))

In the example above:

The client is instructed to pick an ADDRESS_LIST at random and to failover to the other if the chosen ADDRESS_LIST fails. This is indicated by the LOAD_BALANCE and FAILOVER parameters being set to ON.
When an ADDRESS_LIST is chosen, the client first connects to the Oracle Connection Manager, using the Oracle Connection Manager address that uses port 1630 indicated for the ADDRESS_LIST.
The Oracle Connection Manager than connects to the database service, using the listener address indicated for the ADDRESS_LIST.

DESCRIPTIONS and DESCRIPTION_LISTs

DESCRIPTION

Purpose:

Beginning of a connect descriptor, containing the definition of a database listening address and the service name to which to connect. This parameter can be embedded under a DESCRIPTION_LIST.

Example:

net_service_name= (description= (address=...) (connect_data=(service_name=sales.us.acme.com)))

DESCRIPTION_LIST

Purpose:

Defines a list of connect descriptors for a particular net service name

Example:

net_service_name= (description_list= (description= (address=...) (connect_data=(service_name=sales.acme.com))) (description= (address=...) (connect_data=(service_name=sales2.us.acme.com))))

CONNECT_DATA permits 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 (TAF) and should not be confused with the connect-time failover FAILOVER parameter.
See Also:

"Transparent Application Failover for High Availability" for conceptual information

"Configuring Transparent Application Failover" for further complete configuration information

Sub-Parameters

FAILOVER_MODE supports the following sub-parameters:

BACKUP - Specifies the failover node by its net service name. A separate net service name must be created for the failover node.

TYPE - (Required) Specifies the type of failover. Three types of Net8 failover functionality are available by default to Oracle Call Interface (OCI) applications:

SESSION: Fails over the session; that is, if a user's connection is lost, a new session is automatically created for the user on the backup. This type of failover does not attempt to recover selects.

SELECT: Allows users with open cursors to continue fetching on them after failure. However, this mode involves overhead on the client side in normal select operations.

NONE: This is the default, in which no failover functionality is used. This can also be explicitly specified to prevent failover from happening.

METHOD: Determines how fast failover occurs from the primary node to the backup node:

BASIC: Establishes connections at failover time. This option requires almost no work on the backup server until failover time.

PRECONNECT: Pre-establishes connections. This provides faster failover but requires that the backup instance be able to support all connections from every supported instance.

RETRIES: Specifies the number of times to attempts to connect. If DELAY is specified, RETRIES defaults to 5 retry attempts.

DELAY: Specifies the amount of time in seconds to wait between connect attempts. If RETRIES is specified, DELAY defaults to 1 second.

Example:

For implementation examples, see "TAF Implementation".

GLOBAL_NAME

Purpose:

Identifies the Oracle Rdb database. This parameter must be embedded under CONNECT_DATA.

Example:

net_service_name= (description= (address=...) (address=...) (connect_data= (service_name=generic) (rdb_database= [.mf]mf_personal.rdb) (global_name= alpha5)))

HS

Purpose:

Instructs Net8 to connect to a non-Oracle system. This parameter must be embedded under CONNECT_DATA.

Default:

None

Values:

OK

Example:

net_service_name= (description= (address=...) (address=...) (connect_data= (sid=sales6) (hs=ok)))

INSTANCE_NAME

Purpose:

Identifies the database instance to access. The instance name can be obtained from the INSTANCE_NAME parameter in the initialization parameter file.
This parameter must be embedded under CONNECT_DATA.
See Also: "Understanding Connect Descriptors" for information about setting the instance name string

Example:

net_service_name= (description= (address=...) (address=...) (connect_data= (service_name=sales.com) (instance_name=sales1)))

RDB_DATABASE

Purpose:

Specifies the file name of an Oracle RDB database. This parameter must be embedded under CONNECT_DATA.

Example:

net_service_name= (description= (address=...) (address=...) (connect_data= (service_name=sales.com) (rdb_database= [.mf]mf_personal.rdb)))

SERVER

Purpose:

Instructs the listener to connect the client to a specific type of service handle. This parameter must be embedded under CONNECT_DATA.

Values:

DEDICATED | SHARED
DEDICATED connects this client to a dedicated server process.
SHARED connects the client to a shared server.
Note: MTS must be configured in order to connect the client to a shared server.
Note: The USE_DEDICATED_SERVER in the sqlnet.ora file overrides this parameter.

Example:

net_service_name= (description= (address=...) (address=...) (connect_data= (server_name=sales.com) (server=dedicated)))

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 (DB_NAME) and domain name (DB_DOMAIN), entered during installation or database creation.
See Also:

"Database Identification by Service Name Rather than SID" for information about the use of SERVICE_NAME

"Understanding Connect Descriptors" for information on setting the instance name

Example:

net_service_name= (description= (address=...) (address=...) (connect_data= (service_name=sales.com)))

SID

Purpose:

Identifies the database instance for an Oracle8 or Oracle7 database. If the database is Oracle8i, use SERVICE_NAME rather than SID.
See Also: "Database Identification by Service Name Rather than SID"
This parameter must be embedded under CONNECT_DATA.

Example:

net_service_name= (description= (address=...) (address=...) (connect_data= (sid=sales)))

Listener Parameters (listener.ora)

The following items are available in the network listener configuration file (listener.ora).

The listener.ora file is located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows NT, or in the directory specified by the TNS_ADMIN environment variable or registry value.

Listener Address Section

The listener address section of the listener.ora file defines the protocol address(es) of the listener.

DESCRIPTION

Purpose:

Defines listener protocol address(es)
See Also: "Configuring Connections to Non-Oracle Database Services" for configuration information

Example:

listener_name= (description= (address=(protocol=ipc)(key=extproc0)) (address=(protocol=tcp)(host=sales-pc)(port=1521)))

ADDRESS

Purpose:

Defines a listener protocol address. This parameter can be embedded under a ADDRESS_LIST or DESCRIPTION.
See Also: Appendix B for descriptions of the correct parameters to use for each protocol

Example:

listener_name= (description= (address=(protocol=ipc)(key=extproc0)) (address=(protocol=tcp)(host=sales-pc)(port=1521)))

ADDRESS_LIST

Purpose:

Defines lists of listener protocol addresses. If there is only one list of addresses, it is not necessary to use this parameter. This parameter can be embedded under a DESCRIPTION.

Example:

listener_name= (description= (address_list= (address=(protocol=ipc)(key=extproc0)) (address=(protocol=tcp)(host=sales-pc)(port=1521))))

SID_LIST_listener_name Static Service Section

You can use the SID_LIST section of the listener.ora to statically configure service information with the listener.

The SID_LIST is required for backward compatibility with Oracle8 or Oracle7 databases, as well as external procedures and heterogeneous services, and some management tools, including Oracle Enterprise Manager.

Oracle8i database information is dynamically registered with the listener during instance startup. Therefore, this information is not required, unless Oracle Enterprise Manager is used to monitor an Oracle8i database.

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:

GLOBAL_DBNAME

Purpose:

Identifies the global database name of the database, a name comprised of the database name and database domain. You can obtain the GLOBAL_DBNAME value from the SERVICE_NAMES parameter in the initialization parameter file.
This parameter must be embedded under SID_DESC and should match the value of the SERVICE_NAMES parameter.

Example:

sid_list_listener_name= (sid_list= (sid_desc= (global_dbname=oracle.com) (sid_name=orcl) (oracle_home=/usr/oracle)))

ORACLE_HOME

Purpose:

Identifies the Oracle home location of the service. This parameter must be embedded under SID_DESC.

Example:

sid_list_listener_name= (sid_list= (sid_desc= (sid_name=extproc) (oracle_home=/usr/oracle) (program=extproc)))

PROGRAM

Purpose:

Identifies the service's executable program name

Example:

sid_list_listener_name= (sid_list= (sid_desc= (sid_name=extproc) (oracle_home=oracle) (program=extproc)))

SID_NAME

Purpose:

Identifies the Oracle System Identifier (SID) of the instance. You can obtain the SID value from the INSTANCE_NAME parameter in the initialization parameter file.
This parameter must be embedded under SID_DESC.

Example:

sid_list_listener_name= (sid_list= (sid_desc= (global_dbname=oracle.com) (sid_name=orcl) (oracle_home=/usr/oracle)))

SID_LIST

Purpose:

Identifies a list of SID descriptions

Example:

sid_list_listener_name= (sid_list= (sid_desc=...) (sid_desc=...))

SID_DESC

Purpose:

Provides service information for a specific database instance
This parameter can be embedded under SID_LIST.

Example:

sid_list_listener_name= (sid_list= (sid_desc=...) (sid_desc=...))

PRESPAWN_MAX

Purpose:

Specifies the maximum number of prespawned dedicated server processes the listener creates. This number must be at least as many as the sum of the pool size for each protocol. Set this value to a large number so that prespawned dedicated server processes are always available for new connections.
This parameter must be embedded under SID_LIST.
Note: Prespawned dedicated servers cannot be configured on Windows NT.

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

Purpose:

Specifies a list of prespawnd dedicated server process protocol descriptions. This parameter must be embedded under SID_DESC.

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=...)))

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.
See Also: "Configuring 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=...))))

Control Parameters

The following parameters control the behavior of the listener:

CONNECT_TIMEOUT_listener_name

Purpose:

Determines the amount of time in seconds the listener waits for a valid connection request after a connection has been started

Default:

10 seconds

Example:

connect_timeout_listener=12

LOG_DIRECTORY_listener_name

Purpose:

Specifies the destination directory for the listener log file

Default:

$ORACLE_HOME/network/log on UNIX and ORACLE_HOME/network/log on Windows NT

Example:

log_directory_listener=/oracle/network/admin/log

LOG_FILE_listener_name

Purpose:

Specifies the name of the log file for the listener

Default:

listener.log

Example:

log_file_listener=list.log

LOGGING_listener_name

Purpose:

Turns logging on or off

Default:

ON

Values:

ON | OFF

Example:

logging_listener=on

OSS.SOURCE.MY_WALLET

Purpose:

Specifies the location of wallets. Wallets are certificates, keys and trustpoints processed by SSL that allow for secure connections.
See Also: Oracle Advanced Security Administrator's Guide

Default:

None

Example:

oss.source.my_wallet= (source= (method=file) (method_data= (directory=/home/smalladi/oss)))

PASSWORDS_listener_name

Purpose:

Sets an unencrypted password for a listener, so that certain privileges operations, such as SAVE_CONFIG and STOP, used from the LSNRCTL utility are secure. Allows one or more passwords. An encrypted password can set with the LSNRCTL utility's CHANGE_PASSWORD command.

Default:

oracle

Example:

passwords_listener=(oracle8)

SAVE_CONFIG_ON_STOP_listener_name

Purpose:

If set to TRUE, any parameters which were modified through the LSNCRCTL SET command replace prior listener.ora file settings

Default:

FALSE

Example:

save_config_on_stop_listener=true

SSL_CLIENT_AUTHENTICATION

Purpose:

Specifies whether or not a client is authenticated using SSL

Default:

TRUE

Values:

TRUE | FALSE

Usage Notes:

The database authenticates the client. Therefore, this value should be set to FALSE. If this parameter is set to TRUE, the listener attempts to authenticate the client, which can result in a failure.
See Also: Oracle Advanced Security Administrator's Guide

Example:

ssl_cipher_suite=(ssl_dh_dss_with_des_cdc_sha)

STARTUP_WAIT_TIME_listener_name

Purpose:

Sets the number of seconds that the network listener sleeps before responding to the first LSNRCTL STATUS command

Default:

0 seconds

Example:

startup_wait_time_listener=5

TRACE_DIRECTORY_listener_name

Purpose:

Specifies the destination directory for the listener trace files

Default:

$ORACLE_HOME/network/trace on UNIX and ORACLE_HOME/network/trace on Windows NT

Example:

trace_directory_listener=/oracle/network/admin/trace

TRACE_FILE_listener_name

Purpose:

Specifies the name of the trace file for the listener

Default:

listener.trc

Example:

trace_file_listener=list.trc

TRACE_FILELEN_listener_name

Purpose:

Specifies the size of the listener trace files in kilobytes (KB). When the size is met, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_listener_name parameter.

Default:

Unlimited

Example:

trace_filelen_listener=100

TRACE_FILENO_listener_name

Purpose:

Specifies the number of trace files for listener tracing. When this parameter is set along with the TRACE_FILEN_listener_name parameter, trace files are used in a cyclical fashion. The first file is filled first, then the second file, and so on. When the last file has been filled, the first file is re-used, and so on.
The trace file names are distinguished from one another by their sequence number. For example, if the default trace file of listener.trc is used, and this parameter is set to 3, the trace files would be named listener1.trc, listener2.trc and listener3.trc.
In addition, trace events in the trace files are preceded by the sequence number of the file.

Default:

1

Example:

trace_fileno_listener=3

TRACE_LEVEL_listener_name

Purpose:

Turns tracing on/off to a certain specified level

Default:

OFF

Values

OFF - No trace output

USER - User trace information

ADMIN - Administration trace information

SUPPORT - WorldWide Customer Support trace information

Example:

trace_level_listener=admin

TRACE_TIMESTAMP_listener_name

Purpose:

Adds a timestamp in form of dd-month-yyyy hh:mm:ss to a trace event in the listener trace file

Default:

OFF

Values

ON or TRUE | OFF or FALSE

Example:

trace_timestamp_listener=true

USE_PLUG_AND_PLAY_listener_name

Purpose:

Instructs the listener to register database information with an Oracle Names server

Default:

OFF

Values:

ON | OFF

Example:

use_plug_and_play=on

Oracle Names Parameters (names.ora)

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:

Lists the protocol address(es) on which the Oracle Names server listens. Any valid ADDRESS or ADDRESS_LIST is allowed.
See Also:

"ADDRESSes and ADDRESS_LISTs" for a description of address syntax

"Protocol Parameters" for descriptions of the correct parameters to use for each protocol

Default:

names.addresses= (address=(protocol=tcp)(host=oranamesrvr0)(port=1575))

NAMES.ADMIN_REGION

Purpose:

Describes the data source for an administrative region. If set, this parameter defines a database as a repository for information. If this parameter is not set, replication of data between Oracle Names server caches.

Default:

NULL

Example:

names.admin_region= (region= (description= (address=(protocol=tcp) (host=nineva)(port=1575))) (connect_data= (service_name=sales.us.acme.com))) (userid=system) (password=manager) (refresh=172800) (retry=2700) (expire-8700) (version=34619392)) add descriptions for various attributes

NAMES.AUTHORITY_REQUIRED

Purpose:

Determines whether system queries require authoritative answers

Default:

FALSE

Example:

names.authority_required=true

NAMES.AUTO_REFRESH_EXPIRE

Purpose:

Specifies the amount of time in seconds the Oracle Names server caches other region's database server addresses which have been obtained through the NAMES.DOMAIN.HINTS parameter. At the end of this interval, the Oracle Names server issues a query to the other region database servers to refresh the address.

Default:

600 seconds

Acceptable Values:

60-1209600 seconds

Example:

names.auto_refresh_expire=1200000

NAMES.AUTO_REFRESH_RETRY

Purpose:

Specifies the interval in seconds that the Oracle Names server retries the Oracle Names servers on its domain hint list

Default:

180

Minimum Value:

60

Maximum Value

3600

Example:

names.auto_refresh_retry=180

NAMES.CACHE_CHECKPOINT_FILE

Purpose:

Specifies the name and path of the file to which the Oracle Names server writes its checkpoint file.
explain

Default:

$ORACLE_HOME/network/names/ckpcch.ora on UNIX and ORACLE_HOME\network\names\ckpcch.ora on Windows NT

Example:

names.cache_checkpoint_ file=c:\oracle\network\names\cacheck.ora

NAMES.CACHE_CHECKPOINT_INTERVAL

Purpose:

Indicates the interval in seconds in which an Oracle Names server writes a checkpoint of its stored data to a checkpoint file. Each Oracle Names server can periodically write its cached data to a file to protect against startup failures.

Default:

0 (disabled)

Minimum Value:

10 seconds

Maximum Value:

259200 seconds (3 days)

Example:

names.cache_checkpoint_interval=24

NAMES.CONFIG_CHECKPOINT_FILE

Purpose:

Specifies the name and path of the file used to checkpoint Oracle Names server configuration settings

Default:

$ORACLE_HOME/network/names/ckpcfg.ora on UNIX and ORACLE_HOME\network\names\ckpcfg.ora on Windows NT

Example:

names.config_checkpoint_ file=c:\oracle\network\names\configck.ora

NAMES.CONNECT_TIMEOUT

Purpose:

Limits the amounts of time in seconds the Oracle Names server waits for the connection from a client to complete

Default:

3 seconds

Minimum Value:

1 second

Maximum Value:

600 seconds

Example:

names.connect_timeout=8

NAMES.DEFAULT_FORWARDERS

Purpose:

Address list of other Oracle Names servers which are used to forward queries

Example:

names.default_forwarders= (forwarder_list= (forwarder=(name=rootserv1.com)(address=(protocol=tcp) (port=4200)(host=roothost))))

NAMES.DEFAULT_FORWARDERS_ONLY

Purpose:

When set to TRUE, the Oracle Names server forwards queries only to those Oracle Names servers listed as default forwarders with the NAMES.DEFAULT_FORWARDERS parameter

Default:

FALSE

Usage Notes:

If set to FALSE, Oracle Names servers listed as default forwarders are called before Oracle Names servers found in the cache.

NAMES.DOMAIN_HINTS

Purpose:

Lists the names, addresses and domains of all servers in one or more remote regions. Enables the Oracle Names server to know about other regions' Oracle Names servers. This includes at least the root region for all Oracle Names servers who are not in the root region. Other regions can be provided as optimization requires.

Example:

names.domain_hints= (hint_desc=(hint_list= (hint=(name=rootserv1.com) (address=(protocol=tcp)(host=nineva)(port=4200))))

NAMES.DOMAINS

Purpose:

List of domains in the server's local region, as well as the default time to live (TTL) for data in those domains.

Example:

names.domains= (domain_list= (domain=(name=)(min_ttl=86400)) (domain=(name=com)(min_ttl=8640)))

NAMES.FORWARDING_AVAILABLE

Purpose:

If set to ON, the Oracle Names server forwards client request to remote Oracle Names server. If set to OFF, clients without access to the network outside the local domain are unable to resolve names.

Default

ON

Values:

ON | OFF

Example:

names.forwarding_available=off

NAMES.FORWARDING_DESIRED

Purpose:

If set to TRUE, the Oracle Names server provides remote Oracle Names server address location information to clients. This way, clients are redirected to the appropriate Oracle Names server. If set to FALSE, the Oracle Names server connects to the remote Oracle Names server on behalf of clients.

Default:

TRUE

Values:

TRUE | FALSE

Example:

names.forwarding_desired=true

NAMES.KEEP_DB_OPEN

Purpose:

Specifies whether or not to attempt to keep the TNS connection to the region database open between operations. If set to FALSE, the connection is closed after each load, reload or reload-check.

Default:

TRUE

Values:

TRUE | FALSE

Example:

names.keep_db_open=FALSE

NAMES.LOG_DIRECTORY

Purpose:

Specifies the destination directory where the log file for Oracle Names server operational events are written

Default:

$ORACLE_HOME/network/log on UNIX and ORACLE_HOME\network\log on Windows NT

Example:

names.log_directory=c:\oracle\network\names

NAMES.LOG_FILE

Purpose:

Indicates the name of the output file to which Oracle Names server operational events are written. The file name extension is always .log. Do not enter an extension for this parameter.

Default:

NAMES

Example:

names.log_file=onames

NAMES.LOG_STATS_INTERVAL

Purpose:

Specifies the number of seconds between full statistical dumps in the log file

Default:

0 (0=OFF)

Minimum Value:

10 seconds

Maximum Value:

none

Example:

names.log_stats_interval=12

NAMES.LOG_UNIQUE

Purpose:

If set to TRUE, the log file name are unique and do not overwrite existing log files

Default:

FALSE

Values:

TRUE | FALSE

Example:

names.log_unique=true

NAMES.MAX_OPEN_CONNECTIONS

Purpose:

Specifies the number of connections that the Oracle Names server can have open at any given time. The value is generated as the value 10 or the sum of one connection for listening, five for clients, plus one for each remote domain defined in the local administrative region, whichever is greater.
The calculated value is acceptable for most installations.

Default:

Calculated based on entered data.

Minimum Value:

2

Maximum Value:

64

Example:

names.max_open_connections=52

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.MESSAGE_POOL_START_SIZE

Purpose:

Determines the initial number of messages allocated in the server's message pool which are used for incoming or outgoing forwarded messages

Default:

10

Minimum Value:

3

Maximum Value:

256

Example:

names.message_pool_start_size=10

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 an encrypted password for an Oracle Names server, so that certain privileged operations, such as STOP, RESTART and RELOAD, used from the NAMESCTL utility are secure
If this parameter is set with the Net8 Assistant, the password is encrypted. A clear-text password can 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.REGION_CHECKPOINT_FILE

Purpose:

Specifies the name and path of the file used to checkpoint region data (for example, domain addresses, database addresses of Oracle Names servers in the local region)

Default:

$ORACLE_HOME/network/names/ckpreg.ora on UNIX and ORACLE_HOME\network\names\ckpreg.ora on Windows NT

Example:

names.region_checkpoint_ file=c:\oracle\network\names\regionck.ora

NAMES.RESET_STATS_INTERVAL

Purpose:

Specifies the number of seconds during which the statistics collected by the Oracle Names servers should accumulate. At the frequency specified, they are reset to zero. The default value of 0 means never reset statistics.

Default:

0 (never reset)

Minimum Value:

10 seconds

Maximum Value:

none

Example:

names.reset_stats_interval=15

NAMES.SAVE_CONFIG_ON_STOP

Purpose:

If set to TRUE, the Oracle Names server saves its runtime configuration settings back into the names.ora file. Any parameters which were modified through NAMESCTL SET operations replace prior names.ora settings.

Default:

FALSE

Example:

names.save_config_on_stop=FALSE

NAMES.SERVER_NAME

Purpose:

Each Oracle Names server is uniquely identified by a name. All configuration references to a particular Oracle Names server use this name.

Default:

ONAMES_onames_server

Example:

names.server_name=namesrv1.us.oracle.com

NAMES.TRACE_DIRECTORY

Purpose:

Indicates the name of the directory to which trace files from a Oracle Names server trace session are written.

Default:

$ORACLE_HOME/network/trace on UNIX and ORACLE_HOME/network/trace on Windows NT

Example:

names.trace_directory=/oracle/network/admin/trace

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

OFF - No trace output

USER - User trace information

ADMIN - Administration trace information

SUPPORT - WorldWide Customer Support trace information

Example:

names.trace_level=admin

NAMES.TRACE_UNIQUE

Purpose:

Indicates whether each trace file has a unique name, allowing multiple trace files to coexist. If the value is set to ON, a process identifier is appended to the name of each trace file generated.
For example, trace files names namespid.trc are created if the default trace file name, names.trc, is used.

Default:

ON

Values

ON | OFF

Example:

names.trace_unique=on

Oracle Connection Manager Parameters (cman.ora)

The following parameters are available in an Oracle Connection Manager configuration file cman.ora. The cman.ora file is located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows NT, or in the directory specified by the TNS_ADMIN environment variable or registry value.

CMAN

Purpose:

Specifies listening addresses for the 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 the Oracle Connection Manager administrative process, CMADMIN (Oracle Connection Manager Administrative Process)

Default:

cman_admin=(address=(protocol=tcp)(host=anyhost)(port=1830))

Syntax:

cman_admin= ([address_list= ] (address= ...) [(address= ...)])

CMAN_PROFILE

Purpose:

Sets parameters related to the Oracle Connection Manager

Default:

ANSWER_TIMEOUT=0

AUTHENTICATION_LEVEL=0

LOG_LEVEL=0

MAX_FREELIST_BUFFERS=0

MAXIMUM_CONNECT_DATA=1024

MAXIMUM_RELAYS=128

RELAY_STATISTICS=NO

REMOTE_ADMIN=NO

SHOW_TNS_INFO=NO

TRACE_DIRECTORY=$ORACLE_HOME/network/trace on UNIX and ORACLE_HOME\network\trace on Windows NT

TRACE_FILELEN=unlimited

TRACE_FILENO=1

TRACE_TIMESTAMP=NO

TRACING=NO

USE_ASYNC_CALL=YES

Values:

ANSWER_TIMEOUT=[0 to n]

AUTHENTICATION_LEVEL=[0 | 1]

LOG_LEVEL=[0-4]

MAXIMUM_CONNECT_DATA=[257-4096]

MAX_FREELIST_BUFFERS=[0 to 10240]

MAXIMUM_RELAYS=[1 to 2048]

RELAY_STATISTICS=[YES | TRUE | ON | 1 | NO | FALSE | OFF | 0]

REMOTE_ADMIN=[YES | TRUE | ON | 1 | NO | FALSE | OFF | 0]

SHOW_TNS_INFO=[YES | TRUE | ON | 1 | NO | FALSE | OFF | 0]

TRACE_DIRECTORY=directory

TRACE_FILELEN=size of file in KBs

TRACE_FILENO=number

TRACE_TIMESTAMP=[YES | TRUE | ON | 1 | NO | FALSE | OFF | 0]

TRACING=[YES | TRUE | ON | 1 | NO | FALSE | OFF | 0]

USE_ASYNC_CALL=[YES | TRUE | ON | 1 | NO | FALSE | OFF | 0]

Example:

cman_profile= (parameter_list= (maximum_relays=512) (log_level=1) (relay_statistics=yes) (remote_admin=yes) (show_tns_info=yes) (use_async_call=yes) (authentication_level=0) (tracing=yes) (trace_timestamp=yes) (trace_filelen=100) (trace_fileno=2))

CMAN_RULES

Purpose:

Sets the filtering rules for the network access control portion of Oracle Connection Manager
If no rules are specified, all connections are accepted. Use of this feature depends on whether you want to use connection concentration and multi-protocol support features with or without filtering.

Syntax:

cman_rules= (rule_list= (rule= (src=host) (dst=host) (srv= service_name|sid) (act=accept|reject)) [(rule= ...)])

Values:

SRC - Source host name or IP address (in dot notation) of session request

DST - Destination server host name or IP address (in dot notation)

SRV - Database server SID

ACT - Accept or reject incoming requests with the previous characteristics.

Usage Notes

The wildcard for host name is the single character 'x'. In the case of an IP address (d.d.d.d), you can wildcard the individual d's with an 'x'.
If client's connect string contain both SID and SERVICE_NAME, then both names requested need to be permitted by the rules respectively in order for the client's access to be allowed.

Example:

cman_rules= (rule_list= (rule= (src=client1-pc) (dst=sales-pc) (srv= sales.acme.com) (act=reject)) (rule= (src=src=144.25.23.45) (dst=144.25.187.200) (srv= db1) (act=accept)))

Protocol-Specific Parameters (protocol.ora)

Some protocols have platform-specific parameters. These are stored in the protocol.ora file. The protocol.ora file is located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows platforms, or in the directory specified by the TNS_ADMIN environment variable or registry value.

Listed next are some of the common parameters. For a complete listing of parameters for your operating system and platform, see your operating-system-specific documentation.

protocol.EXCLUDED_NODES

Purpose:

Specifies which clients are restricted access to the database.

Syntax:

protocol.excluded_nodes= (hostname | ip_address, hostname | ip_address,...)

Example:

tcp.excluded_nodes= (hr.com, 144.25.5.25)

protocol.INVITED_NODES

Purpose:

Specifies which clients are allowed access to the database. This list takes precedence over the protocol.EXCLUDED_NODES parameter if both lists are present.

Syntax:

protocol.invited_nodes= (hostname | ip_address, hostname | ip_address,...)

Example:

tcp.invited_nodes= (sales.com, 144.185.5.73)

protocol.VALIDNODE_CHECKING

Purpose:

Checks for the protocol.INVITED_NODES and protocol.EXCLUDED_NODES to determine which clients to allow or deny access.

Default:

NO

Values:

YES | NO

Example:

tcp.validnode_checking=yes

TCP.NODELAY

Purpose:

Specifies no delays in buffer flushing within the TCP/IP protocol stack.

Default:

NO

Values:

YES | NO

Example:

tcp.nodelay=yes

Directory Server Access Parameters (ldap.ora)

The following parameters are configured in the ldap.ora file by the Net8 Configuration Assistant on the client and server.

Do not modify these parameters or their settings. The ldap.ora file is located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows platforms, or in the directory specified by the TNS_ADMIN environment variable or registry value.

DIRECTORY_SERVERS

Purpose:

Contains a list of primary and alternate LDAP directory services with their host and port numbers

Values:

host:port[:sslport]

Example:

directory_servers=dlsun1778:389, raffles:400:636

DIRECTORY_SERVER_TYPE

Purpose:

Contains the type of LDAP directory server that is being used

Values:

OID | AD | NDS
OID - Oracle Internet Directory
AD - Microsoft's Active Directory
NDS - Novell Directory Services

Example:

directory_type=oid

DEFAULT_ADMIN_CONTEXT

Purpose:

Specifies the administrative context

Values:

Valid DN

Example:

networkobj_context="o=OracleSoftware,c=US"

Configuration File Changes in Release 8.1

This section describes the following:

Obsolete Parameters for Release 8.1

The following table describes the obsolete parameters for release 8.1:

Parameter File Description

AUTOMATIC_IPC

sqlnet.ora

This parameter used to force sessions through IPC addresses. Due to performance issues, this parameter has been removed. You should configure an IPC address instead.

NAMES.USE_PLUG_AND_PLAY

names.ora

This was used to enable/disable the Dynamic Discovery Option. There are other mechanisms available to discover other Oracle Names server.
See Also: "Configuring the Oracle Names Method"

NAMES.DOMAIN_CHECKPOINT FILE

names.ora

Name of the file used to checkpoint domain data (all the database addresses and other data in the region).
You should use the NAMES.REGION_CHECKPOINT_FILE parameter to create a checkpoint file with this information.

NAMES.TOPOLOGY_CHECKPOINT_FILE

names.ora

Name of the file used to checkpoint topology data (domain addresses of servers in the local region).
You should use the NAMES.REGION_CHECKPOINT_FILE parameter to create a checkpoint file with this information.

Configuration File Syntax Changes

The following table describes the syntax differences between Net8 release 8.0 and Net8 release 8.1:

tnsnames.ora Changes

The following table describes the new parameters in the tnsnames.ora file for Net8 release 8.1:

Parameter Description

FAILOVER

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, as shown in the following:
net_service_name= (description= (failover=on) (address=...) (address=...) (connect_data= (service_name=service_name))) When set to OFF, instructs Net8 to try one address.

By default, this parameter is set to ON for ADDRESS_LISTs, DESCRIPTION_LISTs and a set of DESCRIPTIONs.
Note: Failover during an active session can be configured using Transparent Application Failover parameters, as described in "Configuring Transparent Application Failover".
See Also:

"Configuring Address List Parameters"

"Local Naming Parameters (tnsnames.ora)"

INSTANCE_NAME

In addition to using the SERVICE_NAME parameter, the INSTANCE_NAME parameter can also be used to identify the database instance to access. INSTANCE_NAME is only necessary for an Oracle Parallel server database, where the specific instance to which to connect is important to identify. The following example shows descriptions for a service, op.us.acme.com, that spans multiple instances, op1 and op2. The end user can connect to the op.us.acme.com service through either instance.
net_service_name= (description= (address=...) (connect_data= (service_name=op.us.acme.com) (instance_name=op1))) net_service_name= (description= (address=...) (connect_data= (service_name=op.us.acme.com) (instance_name=op2)))

The INSTANCE_NAME is typically the SID entered during installation or database creation.
See Also: "Understanding Connect Descriptors" for information about the instance name string

LOAD_BALANCE

When set to ON, instructs Net8 to progress through the list of listener addresses in a random sequence, balancing the load on the various listeners, as shown in the following:
net_service_name= (description= (load_balance=on) (address=...) (address=...) (connect_data= (service_name=sales.us.acme.com)))

When set to OFF, instructs Net8 to try the addresses sequentially until one succeeds.
By default, this parameter is set to ON for DESCRIPTION_LISTs.
See Also:

"Configuring Address List Parameters"

"Local Naming Parameters (tnsnames.ora)"

SERVICE_NAME

Identifies the Oracle8i database service to which to connect, as shown in the following:
net_service_name= (description= (address=...) (address=...) (connect_data= (service_name=sales.com)))

The SERVICE_NAME is typically the global database name, a name comprised of the database name and domain name, entered during installation or database creation.
See Also: "Understanding Connect Descriptors" for information about the service name string

cman.ora Changes

The following table describes the new parameters in the cman.ora file for Net8 release 8.1:

Parameter Description

CMAN_ADMIN

Identifies the address for the administrative process CMADMIN process, as shown in the following:
cman_admin= (address= (protocol=tcp) (host= cman-pc) (port=1650)) When the Oracle Connection Manager Control Utility, CMCTL, is run, it locates the CMADMIN protocol address to execute its commands.

It is not necessary to explicitly specify CMAN_ADMIN if you are using the default address of TCP/IP on port 1830.
See Also:

"Enabling Connection Concentration"

"Oracle Connection Manager Control Utility (CMCTL)"

REMOTE_ADMIN

Determines if remote access to an Oracle Connection Manager is allowed.
cman_profile= (parameter_list= (remote_admin=yes))

See Also: "Oracle Connection Manager Control Utility (CMCTL)"

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

NAMESCTL.TRACE_DIRECTORY
Purpose:	Indicates the directory where trace output from the NAMESCTL utility is placed
Default:	`$ORACLE_HOME/network/trace` on UNIX and `ORACLE_HOME``/network/trace` on Windows NT
Example:	namesctl.trace_directory=/oracle/trace

NAMESCTL.TRACE_UNIQUE
Purpose:	Indicates whether a process identifier is appended to the name of each trace file generated, so that several can co-exist
Default:	ON
Values:	ON \| OFF
Example:	namesctl.trace_unique=on

SQLNET.AUTHENTICATION_SERVICES
Purpose:	Enables one or more authentication services. If authentication has been installed, it is recommended that this parameter be set to either NONE or to one of the authentication methods.
Default:	None
Values:	Authentication Available with Net8: NONE - No authentication methods are used. A valid user name and password can be used to access the database. ALL - Enables all authentication methods to be used BEQ - Uses the Bequeath protocol NDS - Uses NDS authentication NTS - Uses Windows NT native authentication Authentication Available with Oracle Advanced Security: KERBEROS5 - Uses Kerberos authentication SECURID - Uses SecurID authentication CYBERSAFE - Uses Cybersafe authentication IDENTIX - Uses Identix authentication RADIUS - Uses RADIUS authentication DCEGSSAPI - Uses DCE GSSAPI authentication See Also: Oracle Advanced Security Administrator's Guide
Example:	sqlnet.authentication_services=(beq, kerberos5, cybersafe)

SQLNET.CLIENT_REGISTRATION
Purpose:	Sets a unique identifier for this client machine. This identifier is passed to the listener with any connection request and is included in the Audit Trail. The identifier can be any alphanumeric string up to 128 characters long.
Default:	None
Example:	sqlnet.client_registration 1432

SQLNET.CRYPTO_CHECKSUM_CLIENT
Purpose:	Specifies the checksum behavior for the client See Also: Oracle Advanced Security Administrator's Guide
Default:	ACCEPTED
Values:	ACCEPTED - Turn on the security service if the other side wants it. REJECTED - Do not turn on the security service even if the other side wants it. REQUESTED - Turn on the security service if the other side allows it. REQUIRED - Turn on the security service or do not make the connection.
Example:	sqlnet.crypto_checksum_client=accepted

SQLNET_CRYPTO_CHECKSUM_TYPE_CLIENT
Purpose:	Specifies a list of crypto-checksum algorithms this client is allowed to use See Also: Oracle Advanced Security Administrator's Guide
Default:	MD5
Values:	MD5 - RSA Data Security's MD5 algorithm
Example:	sqlnet.crypto_checksum_types_client=(md5)

SQLNET.ENCRYPTION_CLIENT
Purpose:	Turns encryption on for the client See Also: Oracle Advanced Security Administrator's Guide
Default:	ACCEPTED
Values:	ACCEPTED - Turn on the security service if the other side wants it. REJECTED - Do not turn on the security service even if the other side wants it. REQUESTED - Turn on the security service if the other side allows it. REQUIRED - Turn on the security service or do not make the connection.
Example:	sqlnet.encryption_client=accepted

SQLNET.ENCRYPTION_TYPES_CLIENT
Purpose:	Specifies a list of encryption algorithms this client is allowed to use See Also: Oracle Advanced Security Administrator's Guide
Default:	All algorithms are used if none are specified.
Values:	One or more of the following: RC4_40 - This is RSA RC4 (40-bit key size) RC4_56 - This is RSA RC4 (56-bit key size) RC4_128 - This is RSA RC4 (128-bit key size) DES - This is Standard DES (56-bit key size) DES40 - This is DES40 (40-bit key size)
Example:	sqlnet.encryption_types_client=(rc4_40)

SQLNET.EXPIRE_TIME
Purpose:	Determines time interval to send a probe to verify the session is alive See Also: Oracle Advanced Security Administrator's Guide
Default:	None
Minimum Value:	0 minutes
Recommended Value:	10 minutes
Example:	sqlnet.expire_time=10

SQLNET.RADIUS_CHALLENGE_RESPONSE
Purpose:	Turns challenge response on or off
Default:	OFF
Values:	ON \| OFF
Example:	sqlnet.radius_challenge_response=ON

SQLNET.RADIUS_SEND_ACCOUNTING
Purpose:	Turns accounting ON and OFF. If enabled, packets are sent to the active RADIUS server at listening port plus one. The default port is 1646 See Also: Oracle Advanced Security Administrator's Guide
Default:	OFF
Values:	ON \| OFF
Example:	sqlnet.radius_send_accounting=ON

SSL_CLIENT_AUTHENTICATION
Purpose:	Specifies whether or not a client--in addition to the server--is authenticated using SSL See Also: Oracle Advanced Security Administrator's Guide
Default:	TRUE
Values:	TRUE \| FALSE
Example:	ssl_cipher_suite=(ssl_dh_dss_with_des_cdc_sha)

SSL_CIPHER_SUITES
Purpose:	Controls what combination of encryption and data integrity is used by SSL See Also: Oracle Advanced Security Administrator's Guide
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. See Also: Oracle Advanced Security Administrator's Guide
Default:	UNDETERMINED
Values:	UNDETERMINED \| 2.0 \| 3.0
Example:	ssl_version=2.0

TNSPING.TRACE_LEVEL
Purpose:	Turns tracing on/off at specified level for the TNSPING utility
Default:	OFF
Values	OFF - No trace output USER - User-induced error conditions trace information ADMIN - Administration trace information SUPPORT - WorldWide Customer Support trace information
Example:	tnsping.trace_level=admin

TRACE_FILE_CLIENT
Purpose:	Specifies the name of the client trace file
Default:	`sqlnet.trc`
Example:	trace_file_client=clientsqlnet.trc

TRACE_FILE_SERVER
Purpose:	Specifies the name of the server trace file
Default:	`svr_``pid``.trc`
Example:	trace_file_server=svrsqlnet.trc

TRACE_FILELEN_CLIENT
Purpose:	Specifies the size of the client trace files in kilobytes (KB). When the size is met, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_listener_name parameter.
Example:	trace_filelen_client=100

C Configuration Parameters