What Is Logging?

• Error information is appended to the log file when an error occurs.

• The log file for a listener includes Audit Trail information about every connection request from a client and most listener control commands. (This feature is new in SQL*Net 2.3.)

• Generally, a log file can be replaced or erased only by an administrator, although client log files can be deleted by the user whose application created them. (Note that in general it is bad practice to delete these files while the program using them is still actively logging.)

• Logging of errors for the client, server, listener, and Names Server cannot be disabled. This essential feature ensures all errors are recorded.

• The Navigator and Connection Manager components of the MultiProtocol Interchange may have logging turned on or off. If on, logging includes connection statistics. The Navigator may optionally log additional information for process or audit control of operations. You set logging parameters using Oracle Network Manager.

Audit Trail

The Audit Trail is a new utility in SQL*Net release 2.3 that enables a system or network administrator to gather and analyze network usage statistics from the log file for the listener. In addition to containing errors, the listener log file contains information about every connection request from a client and most commands sent by the Listener Control Utility. The format of this information makes it easy to use in reports. For example, you might use Audit Trail information in a report about what departments in your company access certain databases most frequently.

For detailed information about log files and the Audit Trail, see Chapter 2, "Logging".