RelationalDBDesignRelationalDBDesign


Logging | Tracing   « Prev  Next »
Lesson 10

Log and Trace File (Conclusion)


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:
  1. The location of the main Oracle trace files is governed by the init.ora parameters.
  2. Log files provide overall information, and trace files offer detailed session information.
  3. Oracle tracing is very resource intensive and should only be used sporadically and for short duration.
  4. Listener tracing can be set in the listsner.ora file, or it can be activated with the “lsnrctl trace” command.
  5. Client tracing involved changing the local sqlnet.ora file, and exiting and re-entering the application.
  6. Trace files can provide highly detailed information about a Net8 connection, but they are rarely used to diagnose connectivity problems.
  7. To diagnose a Net8 connection problem, check.
  8. connectivity to the server (tnsping)
  9. connectivity to the listener (server-side loopback connection)
  10. connectivity from the client to the server.
The next module addresses the important issue of Oracle security in a Net8 environment.

Logging Tracing - Quiz

Before moving on to the next module, click the Quiz button to check your mastery of logging and tracing.
Logging Tracing - Quiz