Oracle Network Products Troubleshooting Guide
Format for Log Parameters
When you use Oracle Network Manager to create or edit the log parameters, you do not need to be concerned about syntax. Use Oracle Network Manager to create or edit the log parameters for all components except the server. See Chapter 5 in Oracle Network Manager Administrator's Guide
Note: There is usually a single SQLNET.ORA file for all the clients and servers on a node. That file would contain log parameters for both clients and servers. Generally all clients on a node will have similar logging requirements, as will all servers.
Editing Log Parameters
Use the following format information when you edit log parameters for the server in the SQLNET.ORA file. Use Network Manager or the SQLNET.ORA Editor to change log parameters for other components.
Log parameters are entered in the appropriate component configuration files in the form:
log_parameter_component = value
The component is one of listener name, client, server, Connection Manager, Navigator, or Names Server.
Note: All log parameters except those for the listener are entered with their component's generic name (for example, navigator). Listener log parameters are entered with the name of the specific listener (for example, LISTENER2). However, the server is the only component for which you should configure log parameters manually. All other components are configured using Oracle Network Manager.
Summary of Available Log Parameters
Parameters are available to control the log filename and location for the client, the server, the listener, and the Names Server. The Connection Manager and the Navigator have these parameters, and in addition both have a parameter that controls whether logging is done.
Logging for the MultiProtocol Interchange
You can turn on logging for both the Connection Manager and the Navigator through a single entry in the Interchange property sheet in Oracle Network Manager. The Navigator has a parameter to control logging of optional information for process and audit control. The Connection Manager has a parameter to control the frequency of logging its statistics. Logging for the pumps is included in the log files for the Connection Manager.
Log Filenames
Log files produced by different components have unique names. The default filenames are:
You can control the name of the log file. For each component, any valid string can be used to create a log filename. The parameters are of the form:
LOG_FILE_component = string
For example:
LOG_FILE_LISTENER = TEST
This parameter would send listener log output to a file called TEST.LOG on the server machine. On most operating systems, the .log suffix is automatically appended to the log filename. Therefore, do not include a suffix in the log filename string.
Some platforms have restrictions on the properties of a filename. See your Oracle operating system-specific manuals for platform-specific restrictions.
Log File Directories
You can control the destination location of the log file for each component. The parameters are of the form:
LOG_DIRECTORY_component = valid directory
Examples are specific to different operating systems. An example on UNIX might be:
LOG_DIRECTORY_LISTENER = /tmp/log
Some platforms have restrictions on the properties of a directory. See your Oracle operating system-specific manuals for platform-specific restrictions.
Logging for Interchange Components
You can set parameters that determine whether or not log files are produced by the Interchange components, the Connection Manager and pumps, and the Navigator. The Navigator has a parameter to control the amount of information collected into a log file. The Connection Manager has a parameter that controls the frequency of logging. These optional parameters are part of the INTCHG.ORA file.
Turning Logging On
By default, the Interchange components do not produce log files. If you want log files to be created, use the Logging page of the Interchange property sheet in Oracle Network Manager.
A single option, Level, determines whether logging is activated for the Connection Manager and the Navigator. The choices and their consequences are as follows:
| OFF | No logging for either the Connection Manager or the Navigator. This is the default. |
| ON | Logging is on for the Connection Manager (and pumps), but not the Navigator. |
| ERRORS | Logging is on for the Connection Manager (and pumps), and all errors of navigation are logged for the Navigator. |
| ALL | Logging is on for the Connection Manager (and pumps), and all navigation requests are logged for the Navigator. |
Setting Logging Intervals for the Connection Manager
The parameter LOG_INTERVAL_CMANAGER indicates the length of the interval between logs of statistics by the Connection Manager, if logging is turned on for that component. Set this parameter using the Logging page of the Interchange property sheet in Oracle Network Manager.
Logging for Pumps
There are no separate log files generated for pumps. All pump log properties are determined by the corresponding Connection Manager parameters.
Note: See the Oracle Network Manager Administrator's Guide for how to set logging parameters for all the network objects.