Oracle Network Products Troubleshooting Guide
How to Set Trace Parameters
There are several ways to set non-default tracing parameters. (For information about defaults see Tables 3-2 tthrough 3-7, and Appendix A.)
- Set non-default tracing parameters in the network definition using Oracle Network Manager.
- Client tracing and server tracing are governed by parameters in the SQLNET.ORA file, set in the Client Profile property sheet.
- Listener tracing is controlled by parameters in the LISTENER.ORA file, set in the Listener property sheet.
- MultiProtocol Interchange component tracing is controlled by parameters in the INTCHG.ORA file, set in the Interchange property sheet.
- Oracle Names tracing is controlled by parameters in the NAMES.ORA file, set in the Names Server property sheet.
Note: If you have a self-configuring network using Oracle Names and the dynamic discovery option, you must add the trace parameters manually to the NAMES.ORA and LISTENER.ORA files.
- Set parameters governing server tracing in the SQLNET.ORA file using a text editor.
- For individual clients, use the SQLNET.ORA Editor, part of the Client Status Monitor. You can turn client tracing on or off and set the level of tracing using this utility. You can also set a non-default name for the trace output file and the directory in which it is stored. See the next chapter for further details.
- For other network components, use the appropriate control utility to turn tracing on and off. For example, using Oracle Network Manager you can set the listener trace level, and non-default name and location for the trace file in the LISTENER.ORA file. To turn tracing on and off, use the TRACE command of the Listener Control Utility. For the correct syntax see Understanding SQL*Net .