|Lesson 4||Oracle tracing parameters|
|Objective||Describe functions of the Oracle trace parameters.|
trace_directory_client sqlnet.oraparameter. If you have set the
trace_unique_clientparameters in your sqlnet.ora file, you will have a
sqlnet_nnn_.trcfile (where nnn is the thread number).
$ORACLE_HOME/network/log.Here you will see the
listener.trcfile for listener traces,
cman_PID.trcfor connection manager traces,
names_nnn_.trcfiles (where nnn is the thread number) for Oracle Names traces, and general server traces as SVR_PID.trc.
c:\orant\network\admin\sqlnet.ora). To change client trace parameters, you must change our local sqlnet.ora file, exit the client application and then re-start the client application.
|listener.ora Parameter||OEM Cloud Control/Net Manager Field||Description|
|TRACE_LEVEL_listener_name||Select a trace level/Trace Level||The level of detail the trace facility records for the listener. The trace level value can either be a value within the range of 0 (zero) to 16 where 0 is no tracing and 16 represents the maximum amount of tracing or one of the following values:
|Trace File||The destination directory and file for the trace file. By default, the directory is ORACLE_HOME/network/trace, and the file name is listener.trc|
|TRACE_FILEAGE_listener_name||You must set this parameter manually.||The maximum age of listener trace files in minutes. When the age limit is reached, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_listener_name parameter.|
|TRACE_FILEAGE_SERVER||You must set this parameter manually.||Specifies the maximum age of server trace files in minutes. When the age limit is reached, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_SERVER parameter.|
|TRACE_FILELEN_listener_name||You must set this parameter manually.||The size of the listener trace files in KB. When the size is reached, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_listener_name parameter|
|TRACE_FILENO_listener_name||You must set this parameter manually.||The number of trace files for listener 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, 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, then 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. When this parameter is set with the TRACE_FILEAGE_listener_name parameter, trace files are cycled based on the age of the trace file. The first file is used until the age limit is reached, then the second file is use, etc..
When the last file's age limit is reached, the first file is re-used.
When this parameter is set with both the TRACE_FILELEN_listener_name and TRACE_FILEAGE_listener_name parameters, trace files are cycled when either the size limit or the age limit is reached.
|TRACE_TIMESTAMP_listener_name||You must set this parameter manually.||A time stamp in the form of dd-mon-yyyy hh:mi:ss:mil for every trace event in the listener trace file.|