|Lesson 6||Enable tracing for Oracle Net components |
|Objective|| Invoke tracing for all Oracle components.|
Enable tracing for Oracle Net Components
The steps used to invoke tracing are outlined here. Each step is fully described in
subsequent sections. The first step is to choose the component to be traced. You may trace a client, a server, or a listener. The steps to enable
tracing are very simple:
- For any component, you can invoke tracing by editing the component configuration file that corresponds to the component traced. The component configuration files are listener.ora, sqlnet.ora or names.ora.
Execute or start the component to be traced. If the trace component configuration files are modified while the component is running, the
modified trace parameters will take effect the next time the component is invoked or restarted. Instructions for each component follow:
- Be sure to turn off tracing when you do not need it for a specific diagnostic purpose.
You can set trace levels to provide different amounts of trace information. For each component, there are three levels of trace information:
- This default setting signifies that no trace output should be generated. The command is:
trace_level_client = off
- This setting is intended for DBAs who do not have extensive network knowledge. The USER trace level generates only English sentences
describing high-level significant networking events. The command is:
trace_level_client = user
- This setting is intended for network administrators with more knowledge of network terms and concepts. The ADMIN trace level generates all of the USER level statements plus additional information such as TNS addresses and detailed events. The ADMIN level of tracing provides the
highest level of detail about Net8 connections. The command is:
trace_level_client = admin
Remember, the trace files are very large. If this parameter is set to USER or ADMIN, the number of large trace files created could interfere with
the available disk space on your machine. Therefore, turn on this parameter only for specific reasons and delete the resulting files when they are
no longer useful.
Note: If an existing trace file from a previous trace session exists and you need to retain the information in it, you will need to save that file under another name. Otherwise Oracle will overwrite the existing trace file.
If you are having trouble pinging a server, and need a detailed trace, you can manually add the following two tracing parameters to your sqlnet.ora file to perform tracing on the TNSPING utility:
The next lesson discusses the location of the log and trace files on an Oracle server.