Net8 Administrator's Guide Release 8.1.6 Part Number A76933-01 |
|
This appendix provides complete listing of all Net8 configuration parameters. It contains the following sections:
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 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.
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: |
|
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 |
LOG_FILE_CLIENT | |
---|---|
Purpose: |
Specifies the name of the log file for the client |
Default: |
|
Example: |
log_file_client=client |
LOG_FILE_SERVER | |
---|---|
Purpose: |
Specifies the name of the log file for the server |
Default: |
|
Example: |
log_file_server=svr.log |
NAMES.DCE.PREFIX | |
---|---|
Purpose: |
Specifies the DCE cell name (prefix) to use for name lookupS |
Default: |
|
Example: |
names.dce.prefix=/.:/subsys/oracle/names |
NAMES.NIS.META_MAP | |
---|---|
Purpose: |
Specifies the map file to be used to map NIS attributes to an NIS mapname |
Default: |
|
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 |
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 |
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.SERVER_PASSWORD | |
---|---|
Purpose: |
Indicates the value that matches the configured password set in the |
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: |
|
Example: |
namesctl.trace_file=nmsctl |
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 |
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 |
Default: |
None |
Example: |
sqlnet.authentication_kerberos5_service= oracle |
SQLNET.AUTHENTICATION_GSSAPI_SERVICE | |
---|---|
Purpose: |
SQLNET.CRYPTO_CHECKSUM_CLIENT | |
---|---|
Purpose: |
|
Default: |
ACCEPTED |
Values: |
|
Example: |
sqlnet.crypto_checksum_client=accepted |
SQLNET.CRYPTO_CHECKSUM_SERVER | |
---|---|
Purpose: |
|
Default: |
ACCEPTED |
Values: |
|
Example: |
sqlnet.crypto_checksum_server=accepted |
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. |
Default: |
qwertyuiopasdfghjkl;zxcvbnm,.s1 |
Example: |
sqlnet.crypto_seed="qwertyuiopasdfghjkl;zxcvbnm,.s1" |
SQLNET.ENCRYPTION_CLIENT | |
---|---|
Purpose: |
|
Default: |
ACCEPTED |
Values: |
|
Example: |
sqlnet.encryption_client=accepted |
SQLNET.ENCRYPTION_SERVER | |
---|---|
Purpose: |
|
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: |
|
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 |
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 |
Default: |
local host |
Example: |
sqlnet.radius_authenetication= officeacct |
SQLNET.RADIUS_AUTHENTICATION_PORT | |
---|---|
Purpose: |
|
Default: |
1645 |
Example: |
sqlnet.radius_authenetication_port= 1667 |
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 |
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 |
|
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: |
|
Example: |
trace_file_client=clientsqlnet.trc |
TRACE_FILE_SERVER | |
---|---|
Purpose: |
Specifies the name of the server trace file |
Default: |
|
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 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 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 |
|
Example: |
trace_level_client=user |
TRACE_LEVEL_SERVER | |
---|---|
Purpose: |
Turns tracing on or off on the server at a specified level |
Default: |
OFF |
Values |
|
Example: |
trace_level_server=admin |
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: |
|
Example: |
use_dedicated_server=on |
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.
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.
net_service_name= (description=(address= (
protocol_address_information))
(connect_data= (service_name=service_name)))
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.
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
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.
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 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:
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:
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:
(address=(protocol=tcp)(host=host1)(port=1630))
(address_list= (failover=on) (load_balance=off) (address=(protocol=tcp)(host=host2a)(port=1630)) (address=(protocol=tcp)(host=host2b)(port=1630))
(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:
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:
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: |
net_service_name=
(description=
( |
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:
|
Sub-Parameters |
FAILOVER_MODE supports the following sub-parameters:
|
Example: |
For implementation examples, see "TAF Implementation". |
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))) |
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 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 |
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:
|
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))) |
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.
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))) |
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:
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_LIST | |
---|---|
Purpose: |
Identifies a list of SID descriptions |
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. 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=...)))) |
The following parameters control the behavior of the listener:
LOG_FILE_listener_name | |
---|---|
Purpose: |
Specifies the name of the log file for the listener |
Default: |
|
Example: |
log_file_listener=list.log |
LOGGING_listener_name | |
---|---|
Purpose: |
Turns logging on or off |
Default: |
ON |
Values: |
ON | OFF |
Example: |
logging_listener=on |
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 |
Default: |
FALSE |
Example: |
save_config_on_stop_listener=true |
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_FILE_listener_name | |
---|---|
Purpose: |
Specifies the name of the trace file for the listener |
Default: |
|
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_LEVEL_listener_name | |
---|---|
Purpose: |
Turns tracing on/off to a certain specified level |
Default: |
OFF |
Values |
|
Example: |
trace_level_listener=admin |
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 |
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:
|
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.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.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_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 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 |
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 . |
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
. 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_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 Attributes | Description |
---|---|
ANSWER_TIMEOUT |
Determines the number of seconds that Oracle Connection Manager uses to time out the protocol handshake associated with an incoming connection request The range is 0 to n. |
AUTHENTICATION_LEVEL |
Determines the level of security the Oracle Connection Manager can enforce: |
LOG_LEVEL |
Determines the level of logging performed by the Oracle Connection Manager:
The CMGW gateway process creates a log file called |
MAX_FREELIST_BUFFERS |
Determines the maximum number of buffers that TNS keeps in its freelist for later re-use instead of returning them to the operating system after a relay gets closed. The range is 0 to 10240. |
MAXIMUM_CONNECT_DATA |
Limits the connect data string length of the incoming connection requests The range is 257 to 4096. |
MAXIMUM_RELAYS |
Determines the maximum number of concurrent connections Oracle Connection Manager supports The range is 1 to 2048. |
RELAY_STATISTICS |
Determines if I/O statistics are recorded YES instructs Oracle Connection Manager to maintain statistics pertaining to relay I/O activities, such as:
This information is stored in the NO records no I/O statistics. |
REMOTE_ADMIN |
Determines if remote access to an Oracle Connection Manager is allowed YES allows access from a remote CMCTL session to Oracle Connection Manager. NO allows only access to the local Oracle Connection Manager. This prevents a user running a remote CMCTL session access to Oracle Connection Manager. |
SHOW_TNS_INFO |
Determines if TNS information are to be recorded
YES instructs Oracle Connection Manager to include TNS information in the NO does not include TNS events in the log file. |
TRACING |
Determines whether or not tracing is enabled for the Oracle Connection Manager
YES enables tracing for the Oracle Connection Manager. The CMGW gateway process creates a trace file called |
TRACE_DIRECTORY |
Specifies the trace directory. You must set this parameter to a non-default location if you plan to use the TRACE_FILELEN or TRACE_TIMESTAMP parameters. |
TRACE_FILELEN |
Specifies the size of the trace file 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 parameter. Note: This parameter requires a non-default trace directory be specified with the TRACE_DIRECTORY parameter. |
TRACE_FILENO |
Specifies the number of trace files for tracing. When this parameter is set along with the TRACE_FILELEN 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 this parameter is set to 3, the CMGW gateway trace files would be named In addition, trace events in the trace files are preceded by the sequence number of the file. |
TRACE_TIMESTAMP |
Adds a timestamp in form of dd-month-yyyy hh:mm:ss to a trace event in the trace file Note: This parameter requires a non-default trace directory be specified with the TRACE_DIRECTORY parameter. |
USE_ASYNC_CALL |
Determines whether or not Oracle Connection Manager uses asynchronous functions while in the answering or calling phase of establishing a Net8 connection YES instructs the Oracle Connection to use all asynchronous functions. NO instructs the Oracle Connection Manager not to use asynchronous functions. Note: Oracle Connection Manager supports out-of-band breaks; it forwards it on to the server. |
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.
TCP.NODELAY | |
---|---|
Purpose: |
Specifies no delays in buffer flushing within the TCP/IP protocol stack. |
Default: |
NO |
Values: |
YES | NO |
Example: |
tcp.nodelay=yes |
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.
DEFAULT_ADMIN_CONTEXT | |
---|---|
Purpose: |
Specifies the administrative context |
Values: |
Valid DN |
Example: |
networkobj_context="o=OracleSoftware,c=US" |
This section describes the following:
The following table describes the obsolete parameters for release 8.1:
Parameter | File | Description |
---|---|---|
AUTOMATIC_IPC |
|
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 |
|
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 |
|
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 |
|
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. |
The following table describes the syntax differences between Net8 release 8.0 and Net8 release 8.1:
Affected element | Net8 release 8.0 | Net8 release 8.1 |
---|---|---|
Connecting with service name and instance name rather than system identifier (SID) in the |
The SID of the database had to be specified in the CONNECT_DATA section of the service_name= (description= (address_list= (address=...) (address=...)) (connect_data=(sid=sales)) |
Because a database can include services that span multiple instances, SID has been replaced by service name and, optionally, instance name.
The following entry allows a client to connect to the net_service_name= (description= (address=...) (address=...) (connect_data= (service_name=sales.com)))
The following entry allows a client to connect to the net_service_name= (description= (address=...) (address=...) (connect_data= (service_name=op.com) (instance_name=op1))) SERVICE_NAME has a value of the global database name, a name comprised of the database name and domain name, and INSTANCE_NAME has a value of the SID, entered during installation or database creation. See Also: |
Client load balancing with DESCRIPTION_LIST and ADDRESS_LIST in the |
DESCRIPTION_LISTs were used for mapping multiple connect descriptors to net service names and for client load balancing of multiple listeners. In order to client load balance, the user had to define separate connect descriptors for each listener. |
While client load balancing is still ON by default for DESCRIPTION_LISTs, load balancing can also be explicitly specified with the new LOAD_BALANCE parameter for an ADDRESS_LIST or associated with a set of ADDRESSes or set DESCRIPTIONs. The following entry associates client load balancing with a list of addresses, affecting all listener ADDRESSes: net_service_name= (description= (load_balance=on) (address=...) (address=...) (connect_data= (service_name=sales.com))) Client load balancing works with any version of the client, but requires an Oracle8i release 8.1 server. See Also: |
Connect-Time Failover with ADDRESS_LIST in the |
An ADDRESS_LIST implied connect-time failover, where a client connect fails over to a different listener if the first listener fails. Net8 and SQL*Net proceeded through all the listener addresses until one succeeded. |
Failover is now supported by default for ADDRESS_LISTs, DESCRIPTION_LISTs, and a set of DESCRIPTIONs. Failover can also be explicitly specified with the new FAILOVER parameter for a set of ADDRESSes. The following entry associates connect-time failover with a list of addresses, affecting all listener ADDRESSes: net_service_name= (description= (failover=on) (address=...) (address=...) (connect_data= (service_name=sales.com))) Connect-time failover works with any version of the client, but requires an Oracle8i release 8.1 server. See Also: |
Routing connections through an Oracle Connection Manager with SOURCE_ROUTE=ON in the |
The SOURCE_ROUTE parameter, which creates a source route of addresses through an Oracle Connection Manager to the destination service, had to be outside of an ADDRESS_LIST: service_name= (description= (source_route=on) (address_list= (address=...) (address=...)) (connect_data= (sid=sales))) |
SOURCE_ROUTE is no longer outside of an ADDRESS_LIST. Instead, it is now associated with a list of ADDRESSes, as shown in the following: net_service_name= (description= (source_route=on) (address=...) (address=...) (connect_data= (service_name=sales.com))) See Also: |
Nested addresses within ADDRESS_LIST in the |
If there was only one list of addresses, it was required to use an ADDRESS_LIST, as shown in the following: service_name= (description= (address_list= (address=...) (address=...)) (connect_data=(sid=sales)) |
Address lists in Net8 do not have to be embedded in an ADDRESS_LIST if there is only one list, as shown in the following: net_service_name= (description= (address=...) (address=...) (connect_data= (service_name=sales.com))) Nested addresses work with any version of the client, but require an Oracle8i database. See Also: |
SID_LIST_listener_name information in the |
The sid_list_listener=(sid_list= (sid_desc= (global_dbname=sales.com) (sid_name=db1) (oracle_home=/usr/bin/oracle))) |
Because database instances and multi-threaded server dispatchers are now automatically registered with the listener, it is no longer necessary to explicitly define database information, unless you are:
See Also: "Configuring Static Service Information" |
Address for CMADMIN process in |
An address was only required for the Oracle Connection Manager gateway process, CMGW. The administrative process, CMADMIN used an internal IPC address. cman=(address=(protocol=tcp)(host=cm an-pc)(port=1630)) |
A protocol address is now required for both CMADMIN and CMGW. This new address is depicted by the new CMAN_ADMIN parameter, as shown in the following: cman=(address=(protocol=tcp) See Also:
|
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: |
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, 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: |
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 |
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: |
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)" |
|
![]() Copyright © 1996-2000, Oracle Corporation. All Rights Reserved. |
|