Trace and Log Parameter Reference
This appendix provides a complete reference to the valid parameters used in controlling tracing and logging in a SQL*Net network. This information is intended to supplement the information presented![[*]](jump.gif)
, "Logging," and Chapter 3,"Tracing." This chapter includes the following information:
- client trace and log parameters
- server trace and log parameters
- listener trace and log parameters
- Connection Manager trace and log parameters
- Navigator trace and log parameters
- Names Server trace and log parameters
- NAMESCTL trace parameters
The name of the component configuration files is of the form component_name.ORA, as in SQLNET.ORA, LISTENER.ORA, INTCHG.ORA, or NAMES.ORA. The actual name of the file may vary on the distribution media for your operating system. For simplicity, this guide consistently refers to SQLNET.ORA, LISTENER.ORA, INTCHG.ORA, and NAMES.ORA files as the configuration files.
Any variations in the filenames and the expected locations of these configuration files and the trace output files are documented in the Oracle operating system-specific manuals for your platform.
Specifying Values in the Component Configuration File
The component configuration file is a short text file that contains a list of parameters and a value for each parameter. Create and modify the configuration files by using Oracle Network Manager. See the Oracle Network Manager Administrator's Guide for information about how to enter or edit information about tracing and logging parameters in the configuration files.
Oracle Network Manager creates lines in the configuration files that look similar to this:
TRACE_LEVEL_CLIENT = ADMIN
TRACE_FILE_CLIENT = CTRACE
Note: There are some parameters in SQLNET.ORA that can be entered and modified through the SQLNET.ORA Editor as well as through Oracle Network Manager. Other parameters can be added or changed only by editing the SQLNET.ORA file with a text editor. These include all parameters for the server, and trace parameters for the NAMESCTL utility.
The following rules govern how you specify parameters in the component configuration files:
- Only parameters and comments should appear in the component configuration file.
- If the configuration file omits a parameter, then the parameter's default value is in effect.
- Parameters can be specified in any order.
- Parameter names are shown in this appendix and this guide in uppercase for readability. Case (upper or lower) is only significant in values if case is significant on the host operating system. Refer to your operating system-specific documentation if you require more information.
- A pound sign (#) is used to start each line that contains a comment.
- Double quotes can surround parameter values, such as filenames. This syntax option is useful for values that contain special characters.
See How to Set Trace Parameters,.
Client Trace and Log Parameter Descriptions
TRACE_LEVEL_CLIENT
This parameter determines the level of trace detail produced for a client application. Setting the trace level to OFF disables trace. Trace should be OFF except for short diagnostic sessions.
Configuration file: SQLNET.ORA
Default value: OFF
OK to change? yes
Range of values: [OFF | USER | ADMIN]
OFF = No user-specified tracing. This value can be used to disable trace.
USER = End-user level: Trace to provide additional information to identify user-induced error conditions such as:
- server installation errors
- runtime show-stopper errors (for example, protocol stack not loaded)
ADMIN = Administrator level: Trace to identify installation-specific problems, for substantiation of "finger pointing" in case of third-party stacks, and for the following situations:
- site configuration-specific failures
(for example, lookup files)
- configuration inconsistencies
- server installation errors
- errors in interaction with third-party software
TRACE_FILE_CLIENT
This parameter controls the trace output filename for a TNS client application. By default, the filename on most operating systems is SQLNET.TRC. A new trace output file is generated for each trace session. A trace session begins when the TNS client application is initiated with valid trace parameters.
Note: Unless a new value for the TRACE_FILE_CLIENT parameter is specified or the old trace file is renamed, or the TRACE_UNIQUE_CLIENT parameter (described next) is set to ON, the new trace output file replaces the old trace output file.
Configuration file: SQLNET.ORA
Default value: SQLNET
OK to change? yes
Ranges of values: valid filename
Example:
TRACE_FILE_CLIENT = CLIENTA
This example generates a trace file called CLIENTA.TRC
Note: On most operating systems, TNS appends the .TRC suffix to the trace filename, so there is no need to specify it in the configuration file.
This parameter determines whether or not a unique trace file is created for each client. By default, the value is OFF, and only one trace file is created for a client. If the value is OFF, when a new trace file is created for a client, it overwrites the existing file. If the value is set to ON, a process identifier is appended to the name of each trace file generated so that several can coexist.
Configuration file: SQLNET.ORA
Default value: OFF
OK to change? yes
Ranges of values: ON|OFF or TRUE|FALSE
The format of the appended process identifier is platform specific and is described in the Oracle operating system-specific manual for your platform. For example, on a UNIX machine the format would be similar to the following:
CLIENTA_3123.TRC
Note: Trace files are usually very large. If this parameter is set to ON (or TRUE), the number of large trace files could interfere with machine performance. Therefore use it carefully.
TRACE_DIRECTORY_
CLIENT
This parameter is used to override the default placement of the trace output file for an Oracle client. By default, the trace output is written in the directory in hich the executable resides. .
Configuration file: SQLNET.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? yes
Ranges of values: valid directory
Example: See your Oracle platform-specific documentation.
LOG_FILE_CLIENT
This parameter controls the log output filename for an Oracle client. By default the log file generated is called SQLNET.LOG. Log files always append new information to the end of the existing log until the administrator prunes the log file.
Configuration file: SQLNET.ORA
Default value: SQLNET
OK to change? yes
Ranges of values: valid filename
Example:
LOG_FILE_CLIENT = CLIENT
This example generates a log file called CLIENT.LOG.
Note: On most operating systems, TNS appends the .LOG suffix to the log filename, so there is no need to specify it in the configuration file.
LOG_DIRECTORY_
CLIENT
This parameter is used to override the default placement of the log output file for an Oracle client. By default, the log file is written in the current directory.
Configuration file: SQLNET.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? yes
Ranges of values: valid directory
Example: See your Oracle platform-specific
documentation.
Server Trace and Log Parameter Descriptions
TRACE_LEVEL_SERVER
This parameter determines the level of trace detail produced for an Oracle server. Setting the trace level to OFF disables trace. Trace should be OFF except for short diagnostic sessions.
Configuration file: SQLNET.ORA
Default value: OFF
OK to change? yes
Range of values: [OFF | USER | ADMIN]
OFF = No user-specified tracing. This value can be used to disable trace.
USER = End-user level: Trace to provide additional information to identify user-induced error conditions such as:
- server installation errors
- runtime show-stopper errors (for example, protocol stack not loaded)
ADMIN = Administrator level: Trace to identify installation-specific problems, for substantiation of "finger pointing" in case of third-party stacks, and for the following situations:
- site configuration-specific failures
(for example, lookup files)
- configuration inconsistencies
- server installation errors
- errors in interaction with third-party software
TRACE_FILE_SERVER
This parameter controls the trace output filename for a TNS client application. By default, the filename on most operating systems is SQLNET.TRC. A new trace output file is generated for each trace session. On most operating systems, each trace file automatically appends the process identifier of the current process to the filename so that previous files are not overwritten. The format of the appended process identifier is platform specific and is described in the Oracle operating system-specific manual for your platform.
Configuration file: SQLNET.ORA
Default value: SQLNET
OK to change? yes
Ranges of values valid filename
Example:
TRACE_FILE_SERVER = SERVERA
On a UNIX machine, this example might generate a trace file called SERVERA_5798.TRC.
Note: On most operating systems, TNS appends the .TRC suffix to the trace filename, so there is no need to specify it in the configuration file.
TRACE_DIRECTORY_ SERVER
This parameter is used to override the placement of the trace output file for an Oracle server. The default location is specific to each operating system. See the Oracle operating system-specific manual for your platform for details.
Configuration file: SQLNET.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? yes
Range of values: valid directory
Example: See your Oracle platform-specific
documentation.
LOG_FILE_SERVER
This parameter controls the log filename for an Oracle server. By default the log file generated is called SQLNET.LOG. Log files always append new information to the end of the existing log until the administrator prunes the log file.
Configuration file: SQLNET.ORA
Default value: SQLNET
OK to change? yes
Ranges of values: valid filename
Example:
LOG_FILE_SERVER = SERVER
This example generates a log file called SERVER.LOG
Note: On most operating systems, TNS appends the .LOG suffix to the log filename, so there is no need to specify it in the configuration file.
LOG_DIRECTORY_ SERVER
This parameter is used to override the placement of the log output file for an Oracle server. The default location is specific to each operating system.
Configuration file: SQLNET.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? yes
Range of values: valid directory
Example: See your Oracle platform-specific
documentation.
TNSPING Utility Trace Parameter Descriptions
TNSPING.TRACE_
LEVEL
This parameter determines the level of trace detail produced for the TNSPING utility. Setting the trace level to OFF disables trace. Trace should be OFF except for short diagnostic sessions.
Configuration file: SQLNET.ORA
Default value: OFF
OK to change? yes
Range of values: [OFF | USER | ADMIN]
OFF = No user-specified tracing. This value can be used to disable trace.
USER = End-user level: Trace to provide additional information to identify user-induced error conditions such as:
- server installation errors
- runtime show-stopper errors (for example, protocol stack not loaded)
ADMIN = Administrator level: Trace to identify installation-specific problems, for substantiation of "finger pointing" in case of third-party stacks, and for the following situations:
- site configuration-specific failures
(for example, lookup files)
- configuration inconsistencies
- server installation errors
- errors in interaction with third-party software
TNSPING.TRACE_
DIRECTORY
This parameter is used to override the placement of the trace output file for the TNSPING utility. The default location is specific to each operating system. See the Oracle platform-specific documentation for details.
Configuration file: SQLNET.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? yes
Range of values: valid directory
Example: .
TNSPING.TRACE_LEVEL = ADMIN
TNSPING.TRACE_DIRECTORY = /usr/bin
Listener Trace and Log Parameter Descriptions
TRACE_LEVEL_
LISTENER
This parameter determines the level of trace detail produced for the network listener. Setting the trace level to OFF disables trace. Trace should be OFF except for short diagnostic sessions.
Configuration file: LISTENER.ORA
Default value: OFF
OK to change? yes
Range of values: [OFF | USER | ADMIN]
OFF = No user-specified tracing. This value can be used to disable trace.
USER = End-user level: Trace to provide additional information to identify user-induced error conditions such as:
- listener installation errors
- runtime show-stopper errors (for example, protocol stack not loaded)
ADMIN = Administrator level: Trace to identify installation-specific problems, for substantiation of "finger pointing" in case of third-party stacks, and for the following situations:
- site configuration-specific failures (for example, lookup files)
- configuration inconsistencies
- listener installation errors
- errors in interaction with third-party software
TRACE_FILE_LISTENER
This parameter controls the trace filename for the listener. By default the trace file generated by the listener is called LISTENER.TRC. Note that for each trace session a trace output file is generated. Unless a new value for TRACE_FILE_LISTENER parameter is specified or the old trace file is relocated or renamed, the new trace output file overwrites the old trace output file.
Note: On most operating systems, the .TRC suffix is automatically appended to the trace filename, so there is no need to specify it in the configuration file.
Configuration file: LISTENER.ORA
Default value: LISTENER
OK to change? yes
Range of values valid filename
Example:
TRACE_FILE_LISTENER = LSNRA
This example generates a trace file called LSNRA.TRC.
Note: If you use a name for the listener other than the default name for the listener (that is, LISTENER), the trace filename would be the name of the non-default listener; for example, LISNAGAIN.TRC.
TRACE_DIRECTORY_ LISTENER
This parameter is used to override the placement of the trace output file for the TNS Listener. The default location is specific to each operating system.
Configuration file: LISTENER.ORA
Default value: See your Oracle platform-specific
documentation
OK to change? yes
Range of values: valid directory
Example: See your Oracle platform-specific
documentation.
LOG_FILE_LISTENER
This parameter controls the log output filename for the Listener. By default the log file generated is called LISTENER.LOG. Log files always append new information to the end of the existing log until the administrator prunes the log file.
Note: If you use a name for the listener other than the default name for the listener (that is, LISTENER), the trace filename would be the name of the non-default listener; for example, LISNAGAIN.TRC.
Configuration file: LISTENER.ORA
Default value: LISTENER
OK to change? yes
Ranges of values: valid filename
Example:
LOG_FILE_LISTENER = LSNR
This example generates a log file called LSNR.LOG
Note: On most operating systems, TNS appends the .LOG suffix to the log filename, so there is no need to specify it in the configuration file.
LOG_DIRECTORY_ LISTENER
This parameter is used to override the placement of the log output file for the listener. By default the log is written in the current working directory.
Configuration file: LISTENER.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? yes
Range of values: valid directory
Example: See your Oracle platform-specific
documentation.
Connection Manager and Pump Trace and Log Parameter Descriptions
TRACE_LEVEL_ CMANAGER
This parameter determines the level of trace detail produced for the Connectio Manager. Setting the trace level to OFF disables trace. Trace should be OFF except for short diagnostic sessions.
Configuration file: INTCHG.ORA
Default value: OFF
OK to change? yes
Range of values: [OFF | USER | ADMIN]
OFF = No user-specified tracing. This value can be used to disable trace.
USER = User level: The tracing at this level is limited.
ADMIN = Administrator level: Trace to identify installation-specific problems, for substantiation of "finger pointing" in case of third-party stacks, and for the following situations:
- site configuration-specific failures (lookup files, and so on)
- configuration inconsistencies
- Interchange installation errors
- errors in interaction with third-party software
This parameter controls the trace output filename for a TNS client application. By default, the filename on most operating systems is SQLNET.TRC. A new trace output file is generated for each trace session. On most operating systems, each trace file automatically appends the process identifier of the current process to the filename so that previous files are not overwritten. The format of the appended process identifier is platform specific and is described in the Oracle operating system-specific manual for your platform.
TRACE_FILE_ CMANAGER
This parameter controls the trace filename for the Connection Manager. By default the trace file generated by the Connection Manager is called CMG.TRC. A new trace output file is generated for each trace session. On most operating systems, each trace file automatically appends the process identifier of the current process to the filename so that previous files are not overwritten. The format of the appended process identifier is platform specific and is described in the Oracle platform-specific documentation.
Configuration file: INTCHG.ORA
Default value: CMG
OK to change? yes
Range of values string
Example:
TRACE_FILE_CMANAGER = CMANAGER
On a UNIX machine, this example might generate a trace file called CMANAGER_4321.TRC, and a pump trace file called PMP_3198.TRC.
Note: On most operating systems, the .TRC suffix is appended to the trace filename automatically, so there is no need to specify it in the configuration file.
Note: All pump trace properties are determined by the corresponding Connection Manager parameters, although a separate trace file is created for a pump. The default name for a pump trace file, PMP_pid.TRC, cannot be changed.
TRACE_DIRECTORY_ CMANAGER
This parameter is used to override the placement of the trace output file for the Connection Manager. The default locaton is specific to each operating system.
Configuration file: INTCHG.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? yes
Range of values: valid directory
Example: See your Oracle platform-specific
documentation.
LOG_FILE_CMANAGER
This parameter controls the log output filename for the Connection Manager. By default, the log file generated is called INTCHG.LOG. Log files always append new information to the end of the existing log until the administrator prunes the log file.
Note: On most operating systems, the .LOG suffix is appended to the log filename automatically, so there is no need to specify it in the configuration file.
Configuration file: INTCHG.ORA
Default value: INTCHG
OK to change? yes
Range of values: string
Example:
LOG_FILE_CMANAGER = CMANAGER
This example generates a log file called CMANAGER.LOG.
Note: Pump statistics are included in the log file for the Connection Manager.
LOG_DIRECTORY_ CMANAGER
This parameter is used to override the placement of the log output file for the Connection Manager. By default, the log is written in the current working directory.
Configuration file: INTCHG.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? Not configurable using Network Manager
Range of values: valid directory
Example: See your Oracle platform-specific
documentation.
This parameter indicates whether the Connection Manager should log information to the log file to maintain Interchange statistics. This is an optional parameter.
Configuration file: INTCHG.ORA
Default value: OFF
OK to change? Use Logging Level field in Network
Manager.
Ranges of values: [OFF | ON]
This parameter indicates the interval between logs of the Interchange statistics in the INTCHG.LOG file.
Note: Setting the log interval to a low value adversely affects Interchange performance, and the log file may become quite large.
Configuration file: INTCHG.ORA
Default value: 60 minutes
OK to change? yes
Ranges of values: 1-99
Navigator Trace and Log Parameter Descriptions
TRACE_LEVEL_ NAVIGATOR
This parameter determines the level of trace detail produced for the Navigator. Setting the trace level to OFF disables trace. Trace should be OFF except for short diagnostic sessions.
The Interchange is not intended to be traced by anyone other than an administrator; so the ADMIN level is recommended for Interchange modules.
Configuration file: INTCHG.ORA
Default value: OFF
OK to change? yes
Ranges of values: [OFF | USER | ADMIN]
OFF = No user-specified tracing. This value can be used to disable trace.
USER = User level: The tracing at this level is limited.
ADMIN = Administrator level: Trace to identify installation-specific problems, for substantiation of "finger pointing" in case of third-party stacks, and for following situations:
- site configuration-specific failures (for example, lookup files)
- configuration inconsistencies
- Navigator installation errors
- errors in interaction with third-party software
- Navigator queries and answers
TRACE_FILE_ NAVIGATOR
This parameter controls the trace filename for the Navigator. By default, the trace file generated by the Navigator is called NAV.TRC. Note that for each trace session a trace output file is generated. Each time a new trace file is created, a process identifier is appended to the name of the trace file so that it is unique. The format of the appended process identifier is platform specific and is described in the Oracle platform-specific documentation.
Configuration file: INTCHG.ORA
Default value: NAV
OK to change? yes
Ranges of values: string
Example:
TRACE_FILE_NAVIGATOR = NAVTEST
On a UNIX machine, this example might generate a trace file called NAVTEST_5234.TRC.
Note: On most operating systems, the .TRC suffix is appended to the trace filename automatically, so there is no need to specify it in the configuration file.
TRACE_DIRECTORY_ NAVIGATOR
This parameter is used to override the placement of the trace output file for the Navigator. The default value is specific to each operating system.
Configuration file: INTCHG.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? yes
Range of values: valid directory
Example: See your Oracle platform-specific
documentation.
LOG_FILE_NAVIGATOR
This parameter controls the log output filename for the Navigator. By default the log file generated is called NAV.LOG. Log files always append new information to the end of the existing log until the administrator prunes the log file.
Configuration file: INTCHG.ORA
Default value: NAVGATR
OK to change? yes
Range of values: string
Example:
LOG_FILE_NAVIGATOR = NAVIGATOR
This example generates a log file called NAVIGATOR.LOG
Note: On most operating systems, the .LOG suffix is appended to the log filename automatically, so there is no need to specify it in the configuration file.
LOG_DIRECTORY_ NAVIGATOR
This parameter is used to override the placement of the log output file for the Navigator. By default, the log is written in the current working directory.
Configuration file: INTCHG.ORA
Default value: See your Oracle platform-specific
documentation.
OK to change? Not configurable using Network Manager
Range of values: valid directory
Example: See your Oracle platform-specific
documentation.
This parameter determines whether the Navigator logs navigation requests. This is an optional parameter.
Configuration file: INTCHG.ORA
Default value: OFF
OK to change? Use Logging Level field in Network
Manager.
Range of values: [OFF|ON]
This parameter takes effect only when the LOGGING_NAVIGATOR parameter is set to ON. LOG_LEVEL_NAVIGATOR determines what requests are logged. Choices are ERRORS and ALL. If ERRORS, then all errors in navigation are logged. If ALL, then all navigation requests are logged.
Configuration file: INTCHG.ORA
Default value: ERRORS
OK to change? yes
Range of values: [ERRORS|ALL]
Names Server Trace and Log Parameter Descriptions
NAMES.TRACE_
LEVEL
This parameter controls the level of trace detailproduced for the Names Server. Setting the level to OFF disables trace. Trace should be OFF except for short diagnostic sessions.
Configuration file: NAMES.ORA
Default value: OFF
OK to change? yes
Ranges of values: [OFF | USER | ADMIN]
OFF = No user-specified tracing. This value can be used to disable trace.
USER = End-user level: Trace to provide additional information to identify user-induced error conditions such as:
- server installation errors
- runtime show-stopper errors (for example, protocol stack not loaded)
ADMIN = Administrator level: Trace to identify installation-specific problems, for substantiation of "finger pointing" in case of third-party stacks, and for the following situations:
- site configuration-specific failures
(for example, lookup files)
- configuration inconsistencies
- server installation errors
- errors in interaction with third-party software
NAMES.TRACE_FILE
This parameter generates the name of the output file from a Names Server trace session. By default the trace file generated by the Names Server is called NAMES. Note that for each trace session a trace output file is generated. On most operating systems, if NAMES.TRACE_UNIQUE is set to ON or TRUE in the NAMES.ORA configuration file, each trace file appends the process identifier of the current process to the filename so that previous files are not overwritten. If files are not overwritten with the process identifier, many files accumulate, which uses up alot of disk space. The format of the appended process identifier is platform specific and is described in Oracle platform-specific documentation.
Configuration file: NAMES.ORA
Default value: names
OK to change? yes
Ranges of values valid filename
Example:
NAMES.TRACE_FILE = NAMES_SUN_03
NAMES.TRACE_UNIQUE = TRUE
On a UNIX machine, this example might generate a trace file called NAMES_5798.TRC.
Note: On most operating systems, TNS appends the .TRC suffix to the trace filename, so there is no need to specify it in the configuration file.
NAMES.TRACE_
DIRECTORY
This parameter determines the name of the directory to which trace files from a Names Server trace session are written. The default value is specific to each operating system.
Note: You must set NAMES.TRACE_DIRECTORY in NAMES.ORA, then restart the Names Server. You cannot set this from NAMESCTL.
Configuration file: NAMES.ORA
Default value: names
OK to change? yes
Range of values: valid directory
Examples: See your Oracle platform-specific
documentation.
This parameter determines whether or not a unique trace file is created for each Names Server. By default, the value is OFF, and only one trace file is created for a Names Server. If the value is OFF, when a new trace file is created for a Names Server, it overwrites the existing file. If the value is set to ON, a process identifier is appended to the name of each trace file generated so that several can coexist.
The format of the appended process identifier is platform specific and is described in the Oracle operating system-specific manual for your platform. For example, on a UNIX machine the format would be similar to the following:
SERVERA_3123.TRC
Note: Trace files are usually very large. If this parameter is set to ON (or TRUE), the number of large trace files could interfere with machine performance. Therefore use it carefully.
NAMES.LOG_FILE
This parameter controls the log filename for an Oracle server. By default the log file generated is called SQLNET.LOG. Log files always append new information to the end of the existing log until the administrator prunes the log file.
Note: On most operating systems, TNS appends the .LOG suffix to the log filename, so there is no need to specify it in the configuration file.
Configuration file: NAMES.ORA
Default value: NAMES.LOG
OK to change? yes
Ranges of values: valid filename
Example:
NAMES.LOG_FILE = names_server2
This example generates a log file called NAMES_SERVER2.
NAMES.LOG_
DIRECTORY
This parameter is used to override the placement of the log output file for a Names Server. The default location is specific to each operating system.
Configuration file: NAMES.ORA
Default value: See your Oracle operating system
documentation.
OK to change? yes
Range of values: valid directory
Example: See your Oracle platform-specific
documentation.
NAMESCTL Utility Trace Parameter Descriptions
NAMESCTL.TRACE_
LEVEL
This parameter indicates the level at which the NAMESCTL program should be traced. It should only be used if NAMESCTL is suspected of causing problems. Setting the level to OFF disables trace. Trace should be OFF except for short diagnostic sessions.
Configuration file: SQLNET.ORA
Default value: OFF
OK to change? yes
Ranges of values: [OFF | USER | ADMIN]
OFF = No user-specified tracing. This value can be used to disable trace.
USER = End-user level: Trace to provide additional information to identify user-induced error conditions such as:
- runtime show-stopper errors (for example, protocol stack not loaded)
ADMIN = Administrator level: Trace to identify installation-specific problems, for substantiation of "finger pointing" in case of third-party stacks, and for the following situations:
- site configuration-specific failures
(for example, lookup files)
- configuration inconsistencies
- errors in interaction with third-party software
NAMESCTL.TRACE_
FILE
This parameter generates the file in which the NAMESCTL trace output is placed. Note that for each trace session a trace output file is generated. On most operating systems, each trace file appends the process identifier of the current process to the filename so that previous files are not overwritten (if NAMESCTL.TRACE_UNIQUE is set to ON). The format of the appended process identifier is platform specific and is described in the Oracle operating system-specific manual for your platform.
Configuration file: SQLNET.ORA
Default value: namesctl
OK to change? yes
Ranges of values valid filename
Example:
NAMESCTL.TRACE_FILE = NC
NAMESCTL.TRACE_UNIQUE = TRUE
On a UNIX machine, this example might generate a trace file called NC_5684.TRC.
Note: On most operating systems, TNS appends the .TRC suffix to the trace filename, so there is no need to specify it in the configuration file.
NAMESCTL.TRACE_
DIRECTORY
This parameter determines the name of the directory to which trace files from a NAMESCTL trace session are written. The default value is specific to each operating system.
Configuration file: SQLNET.ORA
Default value: none
OK to change? yes
Range of values: valid directory
Example: See your Oracle platform-specific
documentation.
NAMESCTL.TRACE_
UNIQUE
This parameter determines whether or not a unique trace file is created for NAMESCTL. By default, the value is OFF, and only one trace file is created for NAMESCTL. If the value is OFF, when a new trace file is created for NAMESCTL, it overwrites the existing file. If the value is set to ON, a process identifier is appended to the name of each trace file generated so that several can coexist.
The format of the appended process identifier is platform specific and is described in the Oracle operating system-specific manual for your platform. For example, on a UNIX machine the format would be similar to the following:
SERVERA_3123.TRC
You must set the NAMESCTL_TRACE_UNIQUE parameter from the SQLNET.ORA configuration file. You cannot set it from NAMESCTL.
Note: Trace files are usually very large. If this parameter is set to ON (or TRUE), the number of large trace files could interfere with machine performance. Therefore use it carefully.
