In this module you learned a great deal about the location usage, definition and application of Oracle log and trace files for Oracle Network Services troubleshooting. The main points of this module include:
- The location of the main Oracle trace files is governed by the init.ora parameters.
- Log files provide overall information, and trace files offer detailed session information.
- Oracle tracing is very resource intensive and should only be used sporadically and for short duration.
- Listener tracing can be set in the listsner.ora file, or it can be activated with the “lsnrctl trace” command.
- Client tracing involved changing the local sqlnet.ora file, and exiting and re-entering the application.
Trace files can provide highly detailed information about a Net8 connection, but they are rarely used to diagnose connectivity problems.
- To diagnose a Net8 connection problem, check.
- connectivity to the server (tnsping)
- connectivity to the listener (server-side loopback connection)
- connectivity from the client to the server.
The next module addresses the important issue of Oracle security in a Net8 environment.