Trace Files

The trace parameters are defined in the same configuration files as are the log parameters. Table 3 - 1 shows the configuration files for different network components and the default names of the trace files they generate.

Table 3 - 1. Trace Parameters and Component Configuration Files

Trace Parameters Corresponding to	Configuration Files	Output Files
Client	SQLNET.ORA	SQLNET.TRC
Server		SQLNET.TRC
TNSPING Utility		TNSPING.TRC
Names Control Utility		NAMESCTL.TRC
Listener	LISTENER.ORA	LISTENER.TRC
Interchange	INTCHG.ORA
Connection Manager		CMG.TRC
Pumps		PMP.TRC
Navigator		NAV.TRC
Names Server	NAMES.ORA	NAMES.TRC

The configuration file for each component is located on the computer running that component.

The trace characteristics for two or more components of an Interchange are controlled by different parameters in the same configuration file. For example, there are separate sets of parameters for the Connection Manager and the Navigator that determine which components will be traced, and at what level.

Similarly, if there are multiple listeners on a single computer, each listener is controlled by parameters that include the unique listener name in the LISTENER.ORA file.

For each component, the configuration files contain the following information:

• a valid trace level to be used (Default is OFF)

• the trace filename (optional)

• the trace file directory (optional)

See the Oracle operating system-specific documentation for your platform to determine where these files are expected to reside and where you can find sample files.