Oracle7 Administrator's Reference for UNIX
Network Files and Utilities
Default Directory
The default directory for global SQL*Net version 2 and MPI files is usually /etc on BSD UNIX systems, and /var/opt/oracle on SVR4 systems.
SQL*Net and MPI search for global files in the following order:
1. The directory specified by $TNS_ADMIN.
2. The /etc or /var/opt/oracle directory.
3. $ORACLE_HOME/network/admin (to search for sqlnet.ora).
If your files are not on the default directory, use the TNS_ADMIN environment variable in the startup files of all network users to specify a different location:
For the Bourne and Korn shell, enter:
$ TNS_ADMIN=new_default
$ export TNS_ADMIN
For the C shell, enter:
% setenv TNS_ADMIN new_default
For each system level configuration file there is also a local private configuration file (stored in the $HOME directory). The settings in the private file override the settings in the system level file.
The adapters Utility
To display installed SQL*Net version 2 protocol adapters, enter:
% adapters
To display adapters linked with an executable, enter:
% adapters $ORACLE_HOME/bin/sqlplus
The following information is displayed:
Installed SQL*Net V2 Protocol Adapters are:
V2 BEQ Protocol Adapter
V2 TCP/IC Protocol Adapter
V2 SPX/IPX Protocol Adapter
Installed network security products are: . . .
SQL*Net v2 Log Output Files
The following files are created when you configure sqlnet.ora and listener.ora to log SQL*Net version 2 components:
| sqlnet.log | receives output for the server process or client applications generated by log parameters set in sqlnet.ora or .sqlnet.ora. This file is in a directory specified in the sqlnet.ora file, typically the $ORACLE_HOME/network/log directory. The sqlnet.log file may be generated by a client application that receives a TNS error. |
| listener_alias.log | is created in the $ORACLE_HOME/network/log directory. There is no default. It receives output generated by listener log parameters in listener.ora. The listener_alias variable is the alias for the TNS listener in the system listener.ora file. |
These files are described in the Oracle Network Products Messages Manual, where they are called SQLNET.LOG and LISTENER.LOG.
TNS listener log files record the start, status, reload, trace, services, version, and stop requests from the lsnrctl listener control utility. Log files also record connect requests and service related requests from MTS.
SQL*Net v2 Trace Output Files
The following files are created when you configure the sqlnet.ora and listener.ora files to trace SQL*Net version 2. These trace file names are the defaults; you can give them different names. The Oracle Network Products Messages Manual describes the trace facility.
Attention: Trace files can get large quickly. Consult your system administrator before enabling them.
| sqlnet.trc | receives output for client applications generated by trace parameters set in sqlnet.ora or .sqlnet.ora. This file is located in a directory specified in the sqlnet.ora file, typically the $ORACLE_HOME/network/trace directory. |
| This file can be unique for every client session by using the trace_unique_client=on in sqlnet.ora parameter. If this parameter is used, the client trace files have the format configured_file_name_pid.trc, where pid is the process ID. The default trace file for both the client and the server is sqlnet.trc, unless you specify separate tracing in the sqlnet.ora file. The sqlnet.trc file is called SQLNET.TRC in the Oracle Network Products Messages Manual. |
| svr_pid.trc | receives output generated by server process trace parameters in the sqlnet.ora file. The pid variable is a process ID. A unique trace file is generated for each server process spawned by the TNS listener. This file is located in a directory specified in the sqlnet.ora file, typically the $ORACLE_HOME/network/trace directory. |
| listener_alias.trc | receives output generated by listener trace parameters in the listener.ora file. There is no default. The listener_alias variable is the alias for the SQL*Net listener specified in the system listener.ora file. The location for this file must be specified in the listener.ora. This file is called LISTENER.TRC in the SQL*Net Administrator's Guide. |
The TNS Listener and its Control Program
The TNS listener is the member of a network community that listens for incoming SQL*Net connections. Following are descriptions of the TNS listener and its control program:
| listener_alias | is the alias for the SQL*Net listener set in the system listener.ora file. When the listener is running, executing the ps command displays the following (although not all systems display listener_alias): |
tnslsnr [listener_alias] [-inherit]
| Shadow processes (dedicated servers) spawned by the SQL*Net listener have the following syntax: |
oracleSID [(LOCAL=NO)]
| lsnrctl | is the control program for the SQL*Net listener process. See Understanding SQL*Net for its syntax. |
See Also: The SQL*Net Administrator's Guide for information about how to designate and configure the TNS listener.
MPI Trace and Log Configuration Files
Following are the log and trace output files for the MPI:
| intchg.log | receives output generated by the connection manager and pump log parameters in the intchg.ora file. This file is created in the $ORACLE_HOME/network/log directory. You can specify an alternative location in the intchg.ora file. |
| navgatr.log | receives output generated by navigator log parameters in intchg.ora. This file is created in the $ORACLE_HOME/network/log directory. You can specify an alternative location in the intchg.ora file. |
| cmg_pid.trc | receives output generated by the connection manager trace parameters in intchg.ora. This file is in a directory specified in intchg.ora, typically the $ORACLE_HOME/network/trace directory. |
| pmp_pid.trc | receives output that refers to the interchange pump, generated by the connection manager trace parameters in the intchg.ora file. This file is in a directory specified in the intchg.ora file, typically the $ORACLE_HOME/network/trace directory. |
| nav_pid.trc | receives output generated by navigator trace parameters in the intchg.ora file. This file is in a directory specified in the intchg.ora file, typically the $ORACLE_HOME/network/trace directory. |
These files are described in the Oracle Network Products Messages Manual, where they are called INTCHG.LOG, NAVGATR.LOG, CMG.TRC, PMP.TRC, and NAV.TRC.
Attention: The trace files for the connection manager and the pump can become large quickly. Consult your system administrator before enabling them.
The Interchange and Control Program
An interchange platform runs the interchange software and at least two network transport protocols. The interchange software connects the networks running the protocols. The platform must also have an intchg.ora file, which defines it as an interchange, and a tnsnet.ora file, which lists all the interchanges in the network and the communities they join. The platform automatically includes a connection manager.
The connection manager listens for connection requests from SQL*Net clients on each of its member communities and uses a data pump to forward the requested data to the destination. One connection manager can manage more than one data pump.
The name of the interchange process which includes the connection manager is intlsnr. When a data pump is forked by the connection manager, its process name is intpump.
A navigator selects the best connection paths for connections that span communities. Navigators require a tnsnav.ora file, which identifies the communities it belongs to and lists the navigators in each community. The navigator accesses the interchange tnsnet.ora file, which lists the TNS communities on the network and identifies the interchanges for each community. The navigator process name is navgatr.
The control program for interchange and navigator processes is intctl, called INTCTL in the Oracle Multiprotocol Interchange Administrator's Guide.