Oracle Network Products Troubleshooting Guide

Contents Index Home Previous Next

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:

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:

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.

TRACE_UNIQUE_ CLIENT

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.

Contents Index Home Previous Next