Troubleshooting Oracle Net Services

Go to main content 24/26 16 Troubleshooting Oracle Net Services

Oracle Net Services provides methods for understanding and resolving network problems through the use of log and trace files. These files keep track of the interaction between network components as errors occur. Evaluating this information will help you to diagnose and troubleshoot even the most complex network problems.

This chapter describes common network errors and outlines procedures for resolving them. It also describes methods for logging and tracing error information to diagnose and troubleshoot more complex network problems. This chapter contains these topics:

• Diagnosing Net Services

• Resolving the Most Common Error Messages for Oracle Net Services

• Troubleshooting Tips from the Field for Oracle Net Services

• Troubleshooting the TNS-12154 Error

• Troubleshooting Network Problems Using Log and Trace Files

• Logging Error Information for Oracle Net Services

• Tracing Error Information for Oracle Net Services

• Contacting Oracle Support Services

Diagnosing Net Services

If an attempt to make a basic peer-to-peer (single protocol network) connection returns an ORA Error, this section may help you diagnose the cause of the problem.

Any underlying fault, noticeable or not, is reported by Net Services with an error number or message that is not always indicative of the actual problem. This section helps you determine which parts of Net8 Services do function properly rather than the parts that do not work. It also helps you to decide in which of the following categories the fault belongs:

• Oracle software

• Operating system layer

• Other network layers

Testing the various network layers progressively should in most cases uncover any problem.

Server Diagnostics

Note:

You may need assistance from your server administrator to follow the instructions in this section.

Answer the following questions:

• Is any other system (workstation/server) able to connect to the server using Net8?

• Has the server, database, or listener configuration remained the same for some time?

If you answered YES to any of the preceding questions/statements, then skip this section and continue to "Client Diagnostics".

If you are unsure, or answered NO to any of the preceding questions, then continue.

Diagnosing Net8 Services on the server involves the following tasks:

• Task 1: Verify the Database Is Running

• Task 2: Perform a Loopback Test

Task 1: Verify the Database Is Running

To check that the database is up, login to the database and connect with a valid username and password. For example:

SQLPLUS system/manager

A message appears, confirming that you are connected with the database. If you receive the following errors, ask your Database Administrator to assist you:

• ORA-1017: invalid U/P

• ORA-1034: Oracle not available

Task 2: Perform a Loopback Test

To perform a loopback test from the server to the database:

1. Ensure that the listener.ora, tnsnames.ora, and sqlnet.ora files exist in the correct locations, as described in "Localized Configuration File Support".

2. Follow the instructions in "Testing Configuration on the Database Server" to perform a loopback test.

   • If the loopback test continues to fail, continue to the next step.

   • If the loopback test passes, skip to "Client Diagnostics".

3. Check the Problem/Solution Database Web site at http://support.oracle.com for more specific information on the error received, or contact Oracle Worldwide Support.

Client Diagnostics

At this point, you know the serverside listener works properly, because you could verify at least one of the following statements:

• The database server passed a loopback test, showing that the connection worked.

• Other computers connect also using Net8 Services to this same database.

• Connections from this workstation worked previous to making changes on this computer, such as the installation of a new product or a modification to the network configuration.

To perform diagnostics on the client:

1. Check that you have installed the same protocol support as was installed on the database server.

   On UNIX you can use the ADAPTERS utility to verify protocol support. On the database server, run the adapters 'which oracle' command from $ORACLE_HOME/bin to display the protocol support, naming methods, and security options linked with the oracle executable. The adapters utility displays output similar to the following:

   Oracle Net transport protocols linked with ./oracle are: IPC BEQ TCP/IP SSL RAW Oracle Net naming methods linked with ./oracle are: Local Naming (tnsnames.ora) Oracle Directory Naming Oracle Host Naming NIS Naming Oracle Advanced Security options linked with ./oracle are: RC4 40-bit encryption RC4 56-bit encryption RC4 128-bit encryption RC4 256-bit encryption DES40 40-bit encryption DES 56-bit encryption 3DES 112-bit encryption 3DES 168-bit encryption AES 128-bit encryption AES 192-bit encryption AES 256-bit encryption MD5 crypto-checksumming SHA crypto-checksumming (for FIPS) SHA-1 crypto-checksumming Kerberos v5 authentication RADIUS authentication ENTRUST authentication

   On the client, run the adapters command from $ORACLE_HOME/bin to display the configured Oracle protocol support, naming methods, and security options. The ADAPTERS utility displays output similar to the following:

   Installed Oracle Net transport protocols are: IPC BEQ TCP/IP SSL RAW Installed Oracle Net naming methods are: Local Naming (tnsnames.ora) Oracle Directory Naming Oracle Host Naming NIS Naming Installed Oracle Advanced Security options are: RC4 40-bit encryption RC4 56-bit encryption RC4 128-bit encryption RC4 256-bit encryption DES40 40-bit encryption DES 56-bit encryption 3DES 112-bit encryption 3DES 168-bit encryption AES 128-bit encryption AES 192-bit encryption AES 256-bit encryption MD5 crypto-checksumming SHA-1 crypto-checksumming Kerberos v5 authentication RADIUS authentication ENTRUST authentication

   Note:

   RAW is an internal protocol used by Oracle Net.

   See Also:

   Oracle UNIX operating system-specific Administrator's Reference for further information about the adapters utility

2. Check base connectivity for underlying network transport. Net8 technology depends on the underlying network for a successful connection.

   Protocol	Verify that you can...
   TCP/IP	Use terminal emulation or file transfer utilities, (PING, FTP, TELNET) from the client to the database server.
   Named Pipes	See other computers or servers on the Microsoft network. Ensure that you are able to share drives within the network.

   Resolving the Most Common Error Messages for Oracle Net Services

   Due to the complexity of network communications, network errors may originate from a variety of sources, for a variety of reasons. If an error occurs, applications such as SQL*Plus, that depend on network services from Oracle Net Services, will normally generate an error message.

   A list of the most common network error messages follows:

   • ORA-03113: TNS:end-of-file on communication channel

   • ORA-03121: no interface driver connection - function not performed

   • ORA-12154: TNS:could not resolve service name

   • ORA-12170: TNS:Connect timeout occurred

   • TNS-12500/ORA-12500: TNS: listener failed to start a dedicated server process

   • ORA-12514: TNS:listener does not currently know of service requested in connectdescriptor

   • ORA-12520: TNS:listener could not find available handler for requested type of server

   • ORA-12521: TNS:listener could not resolve INSTANCE_NAME given in connect descriptor

   • ORA-12525: TNS:listener has not received client's request in time allowed

   • ORA-12533: TNS:illegal ADDRESS parameters

   • TNS-12540/ORA-12540: TNS:internal limit restriction exceeded and TNS-00510: Internal limit restriction exceeded

   • TNS-12541/ORA-12541: TNS:no listener

   • TNS-12549/ORA-12549: TNS:operating system resource quota exceeded and TNS-00519: Operating system resource quota exceeded

   • TNS-12560/ORA-12560: TNS:protocol adapter error occurred

   See Also:

   Oracle Database Error Messages for a complete listing of error messages ORA-03113: TNS:end-of-file on communication channel Cause: An error has occurred on the database server. Action: Check the alert_sid.log on the server. The location of alert_sid.log is specified by the BACKGROUND_DUMP_DEST initialization parameter. An unexpected end of file was processed on the communication channel. This may be an indication that the communications link may have gone down at least temporarily; it may indicate that the server has gone down.You may need to modify your retransmission count. ORA-03121: no interface driver connection - function not performed Cause: A SQL*Net version 1 prefix was erroneously used in the connect string. Action: Do not use the following prefixes in the connect string.

   • T:

   • X:

   • P:

   The username and password were specified from a client computer that had no local Oracle database installed.Specify a connect string.

   ORA-12154: TNS:could not resolve service name Cause: Oracle Net could not locate the net service name specified in the tnsnames.ora configuration file. Action: Perform these steps:

   1. Verify that a tnsnames.ora file exists.

      See Also:

      "Localized Configuration File Support" for configuration file location information

   2. Verify that there are not multiple copies of the tnsnames.ora file.

   3. In the tnsnames.ora file, verify that the net service name specified in your connect string is mapped to a connect descriptor.

   4. Verify that there are no duplicate copies of the sqlnet.ora file.

   5. If you are using domain names, verify that your sqlnet.ora file contains a NAMES.DEFAULT_DOMAIN parameter. If this parameter does not exist, you must specify the domain name in your connect string.

   6. If you are not using domain names, and this parameter exists, delete it or disable it by commenting it out.

   7. If you are connecting from a login dialog box, verify that you are not placing an "@" symbol before your connect net service name.

   8. Activate client tracing and repeat the operation.

   Cause: Oracle Net could not locate the database service name or net service name specified in the directory server. Action: Perform these steps:

   1. Verify that the database service or net service name entry exists in the directory that this computer was configured to use.

      See Also:

      Oracle Internet Directory Administrator's Guide for directory setup instructions

   2. Verify that the sqlnet.ora file includes the following entry:

      NAMES.DIRECTORY_PATH=(ldap, other_naming_methods)
   ORA-12170: TNS:Connect timeout occurred Cause: The client failed to establish a connection and complete authentication in the time specified by the SQLNET.INBOUND_CONNECT_TIMEOUT parameter in the sqlnet.ora file. This error may be a result of network or system delays, or it may indicate that a malicious client is trying to cause a denial-of-service attack on the database server.

   See Also:

   "Configuring the Listener and the Oracle Database To Limit Resource Consumption By Unauthorized Users" further information about setting the SQLNET.INBOUND_CONNECT_TIMEOUT parameter Action: If the error occurred due to system or network delays that are normal for the particular environment, then perform these steps:

   1. Turn on tracing to determine where clients are timing out.

      See Also:

      "Tracing Error Information for Oracle Net Services"

   2. Reconfigure the SQLNET.INBOUND_CONNECT_TIMEOUT parameter in sqlnet.ora to a larger value.

   If you suspect a malicious client, then perform these steps:

   1. Locate the IP address of the client in the sqlnet.log file on the database server to identify the source.

      For example, the following sqlnet.log excerpt shows a client IP address of 10.10.150.35.

      Fatal NI connect error 12170. VERSION INFORMATION: TNS for Solaris: Version 10.1.0.2.0 Oracle Bequeath NT Protocol Adapter for Solaris: Version 10.1.0.2.0 TCP/IP NT Protocol Adapter for Solaris: Version 10.1.0.2.0 Time: 03-JUL-2002 13:51:12 Tracing to file: /ora/trace/svr_13279.trc Tns error struct: nr err code: 0 ns main err code: 12637 TNS-12637: Packet receive failed ns secondary err code: 12604 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.150.35)(PORT=52996))

      Beware that an IP address can be forged.

      If the time out occurs before the IP address can be retrieved by the database server, then enable listener tracing to determine the client that made the request.

      See Also:

      Tracing Error Information for Oracle Net Services

   2. Restrict access to the client. For example, you can configure parameters for access rights in the sqlnet.ora file.

      See Also:

      "Configuring Database Access Control"
   TNS-12500/ORA-12500: TNS: listener failed to start a dedicated server process Cause: The listener failed to start the oracle program. Possible reasons include:

   • The maximum number of processes allowed for a single user was exceeded

   • The listener does not have execute permission on the oracle program

   • The associated Windows service is not started

   In some cases, these errors can be caused by the same conditions which cause TNS-12549/ORA-12549, TNS-00519, TNS-12540/ORA-12540, TNS-00510, and TNS-12560/ORA-12560 errors.

   Action: Perform the appropriate action:

   • Increase the number of processes by setting the PROCESSES parameter in the database initialization file to a larger value.

   • Check the listener.log file for detailed error stack information.

   ORA-12514: TNS:listener does not currently know of service requested in connectdescriptor Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that has either not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener. Action: Perform these steps:

   1. Wait a moment and try to connect a second time.

   2. Check which services are currently known by the listener by executing the Listener Control utility STATUS or SERVICES command.

      See Also:

      "Determining the Current Status of a Listener" and "Monitoring Services of a Listener"

   3. Check that the SERVICE_NAME parameter in the connect descriptor specifies a service name known by the listener.

   4. Check for an event in the listener.log file.

      See Also:

      "Analyzing Listener Log Files"
   ORA-12520: TNS:listener could not find available handler for requested type of server Cause: The type of service handler requested by the client is incorrect or not registered for the requested SERVICE_NAME/INSTANCE_NAME, or the database instance is not registered with the listener. Action: If you suspect the problem is the wrong type of service handler, perform these steps:

   1. If (server=value) is set is in the connect descriptor, ensure that the value is set to the appropriate service handler type for the database, that is, dedicated for dedicated server or shared for dispatchers. You can use the Listener Control utility SERVICES command to see what service handlers are currently registered with the listener.

      See Also:

      "Monitoring Services of a Listener"

   2. If USE_DEDICATED_SERVER is set to ON in the sqlnet.ora file, then ensure the database is configured to use dedicated servers. If it is not, set this parameter to off.

   3. Ensure that the database instance is running. If the instance not running, start it so that it can register with the listener.

   ORA-12521: TNS:listener could not resolve INSTANCE_NAME given in connect descriptor Cause: The INSTANCE_NAME in the connect descriptor is incorrect, or the database instance is not registered with the listener. Action: Perform these steps:

   1. Check to make sure the service name specified in the connect descriptor is correct.

   2. Ensure the database instance is running. If the instance not running, start it so that it can register with the listener. You can use the Listener Control utility SERVICES command to see what instances are currently registered with the listener.

      See Also:

      "Monitoring Services of a Listener"
   ORA-12525: TNS:listener has not received client's request in time allowed Cause: The client failed to complete its connect request in the time specified by the INBOUND_CONNECT_TIMEOUT_listener_name parameter in the listener.ora file. This error may be a result of network or system delays, or it may indicate that a malicious client is trying to cause a denial-of-service attack on the listener.

   See Also:

   "Configuring the Listener and the Oracle Database To Limit Resource Consumption By Unauthorized Users" for further information about setting the INBOUND_CONNECT_TIMEOUT_listener_name parameter Action: If the error occurred due to system or network delays that are normal for the particular environment, then reconfigure the INBOUND_CONNECT_TIMEOUT_listener_name parameter in listener.ora to a larger value.

   If you suspect a malicious client, then perform these steps:

   1. Locate the IP address of the client in listener.log to identify the source.

      For example, the following listener.log excerpt shows a client IP address of 10.10.150.35.

      03-JUL-2002 16:42:35 * <unknown connect data> * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.150.35)(PORT=53208)) * establish * <unknown sid> * 12525 TNS-12525: TNS:listener has not received client's request in time allowed TNS-12604: TNS: Application timeout occurred

      Beware that an IP address can be forged.

   2. Restrict access to the client. For example, you can configure parameters for access rights in the sqlnet.ora file.

      See Also:

      "Configuring Database Access Control"
   ORA-12533: TNS:illegal ADDRESS parameters Cause: The protocol specific parameters in the ADDRESS section of the designated connect descriptor are incorrect. Action: Correct the protocol address.

   See Also:

   Oracle Database Net Services Reference for correct protocol syntax TNS-12540/ORA-12540: TNS:internal limit restriction exceeded and TNS-00510: Internal limit restriction exceeded Cause: An internal limit has been exceeded. Possible limits include:

   • Number of open connection that Oracle Net can process simultaneously

   • Number of memory buffers which can be used simultaneously

   • Number of processes a particular database instance is allowed

   The first two are examples of hard limits. The third is an example of a limit which can be increased by setting PROCESSES parameter in the database initialization file to a larger value. In this case, a TNS-12500/ORA-12500 error is also returned. In some cases, these errors can be caused by the same conditions which cause TNS-12549/ORA-12549 and TNS-00519 errors.

   Action: Perform these steps:

   Wait for the open connections to close and retry. If the error persists, then check the sqlnet.log or listener.log file for detailed error stack information.

   TNS-12541/ORA-12541: TNS:no listener Cause: The connection request could not be completed because the listener is not running. Action: Perform these steps:

   Ensure that the supplied destination address matches one of the addresses used by the listener.Verify that this is not a version compatibility problem.

   TNS-12549/ORA-12549: TNS:operating system resource quota exceeded and TNS-00519: Operating system resource quota exceeded Cause: A quota or hard limit imposed by the operating system has been exceeded.

   Possible limits include:

   • The maximum number of processes allowed for a single user

   • The operating system is running low on paging space

   Action: Perform the appropriate action:

   • Increase the number of processes by setting the PROCESSES parameter in the database initialization file to a larger value.

   • Check the sqlnet.log or listener.log file for detailed error stack information, such as an operating system error code to help identify which quota has been exceeded.

   TNS-12560/ORA-12560: TNS:protocol adapter error occurred Cause: There was an error when using a particular protocol. This error may be due to incorrect configuration of an ADDRESS parameter or may occur due to errors returned from the underlying protocol or operating system interface.

   In some cases, these errors will be caused by the same conditions which cause TNS-00510, TNS-00519, TNS-12540/ORA-12540, TNS-12549/ORA-12549 errors.

   Action: Check the sqlnet.log or listener.log file for detailed error stack information.

   Troubleshooting Directory Naming Errors

   Directory naming issues associated with connectivity errors such as ORA-12154, ORA-12543, or ORA-12541 for database service or net service name entries in a directory server require analysis of the data. You can analyze the data contained within a directory server with the ldifwrite command line tool.

   ldifwrite enables you to convert all or part of the information residing in a directory server to LDAP Data Interchange Format (LDIF). The ldifwrite tool performs a subtree search, including all entries following the specified distinguished name (DN), including the DN itself.

   The ldifwrite tool syntax is as follows:

   ldifwrite -c net_service_name/database_service -b base_DN -f ldif_file

   Table 16-1 ldapwrite Arguments

   Argument	Description
   -c net_service_name/database_service	Specify the net service name or database service name that will connect you to the directory server.
   -b base_DN	Specify the base of the subtree to be written out in LDIF format.
   -f ldif_file	Specify the input file name.

   The following example writes all the directory naming entries under dc=us,dc=acme,dc=com to the output1.ldi file:

   ldifwrite -c ldap -b "dc=us,dc=acme,dc=com" -f output.ldif

   Troubleshooting Tips from the Field for Oracle Net Services

   Here are some tips you may find helpful when you are having difficulty diagnosing network problems:

   • Use the node or network address during configuration instead of the name of the server computer

     This eliminates any internal lookup problems and make the connection slightly faster.

   • If you are using TCP/IP addresses, use the IP address rather than host name

     For example, change the (HOST=server_name) line in the tnsnames.ora file with the internet address, for example (HOST=198.32.3.5).

   • Perform a loopback test

     Perform a loopback test on the server as described in "Testing Configuration on the Database Server". If the test passes, ftp the tnsnames.ora and sqlnet.ora files to the client.

   • Check what is between you and the server

     If it is a wide area network (WAN), identify any intermediate systems that may not work correctly. If all computers are fine, the problem may be a timing issue.

   • Verify whether or not there is a timing issue

     Timing issues are associated with an ORA-12535 error in the client log files.

     To resolve this, try speeding up the connection by using exact addresses instead of names and increase the INBOUND_CONNECT_TIMEOUT_listener_name parameter in the listener.ora file. The default value for this parameter is 10 seconds.

   • Determine which Oracle applications are failing

     SQL*Plus may work, but CASE tools may not. If you determine the problem is a data volume issue, try to transfer a large (5 MB) file with the base connectivity.

   Questions to Ask When Troubleshooting Oracle Net Services

   Here are some questions to ask yourself when diagnosing a problem:

   • Do all computers have a problem, or is it just one?

     If one computer works and another does not, and you are confident that the same software (Oracle and third-party products) is installed, on each computer, swap out the network cables, if they are close enough, to see if the problem moves. If it does move, it indicates that the problem has something to do with the client/server connection and is not local to the PC.

   • What kind of links exist between the client and the server, for example, X.25, ISDN, Token Ring, or leased line?

     Sniffers and LAN analyzers are useful for intermittent failing connections or detecting time outs and resent packets. You can also see what side of the conversation is waiting for a response.

   Troubleshooting the TNS-12154 Error

   This section offers some solutions to the TNS-12154 error. The TNS-12154 error is encountered when SQL*Net cannot find the alias specified for a connection in the TNSNAMES.ORA file or other naming adapter.

   Before attempting to resolve the problem, it may be helpful to have a print out or view of both the TNSNAMES.ORA file and the SQLNET.ORA file. Looking at these files at the same time is helpful since references will be made to both.

   • Problem Description

   • Troubleshooting TNS-12154 on UNIX

   • Troubleshooting TNS-12154 onWindows NT

   • Troubleshooting TNS-12154 on Windows 95/98

   • Troubleshooting TNS-12154 on Windows 3.1

   • Oracle Database Links

   • Oracle Names

   • LDAP

   • Operating System Search Path for Configuration Files

   Problem Description for TNS-12154

   The TNS-12154 error appears when SQL*Net cannot find the alias specified for a connection in the TNSNAMES.ORA file or other naming adapter.

   Before attempting to resolve this problem, it is helpful to print out or view both the TNSNAMES.ORA file and the SQLNET.ORA file. Looking at these files at the same time is helpful because references will be made to both.

   TNSNAMES.ORA and SQLNET.ORA are located in the default network administration directory <<<on the client machine.>>>

   Troubleshooting TNS-12154 on UNIX

   Be sure that the TNSNAMES.ORA file and the SQLNET.ORA file resemble the following examples.

   Example 16-1 TNSNAMES.ORA Sample

   DEV1.WORLD = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (Host = 145.45.78.56) (Port = 1521) ) ) (CONNECT_DATA = (SID = ORCL) ) )

   Example 16-2 SQLNET.ORA Sample

   TRACE_LEVEL_CLIENT = OFF SQLNET.AUTHENTICATION_SERVICES = (NONE) NAMES.DIRECTORY_PATH = (TNSNAMES) AUTOMATIC_IPC = OFF

   Troubleshooting Network Problems Using Log and Trace Files

   Oracle Net Services provide detailed information about the source and context of problems as they arise. This information is generated and stored in log and trace files. The process of logging and tracing error information will help you to diagnose and resolve network problems.

   Logging Error Information for Oracle Net Services

   All errors encountered in Oracle Net Services are appended to a log file for evaluation by a network or database administrator. The log file provides additional information for an administrator when the error message on the screen is inadequate to understand the failure. The log file, by way of the error stack, shows the state of the software at various layers.

   To ensure that all errors are recorded, logging cannot be disabled on clients or Names Servers. Furthermore, only an administrator may replace or erase log files. The log file for the listener also includes Audit Trail information about every client connection request, as well as most listener control commands.

   This section contains these topics:

   • Oracle Net Error Stacks

   • Oracle Net Services Log File Names

   • Setting Logging Parameters

   • Setting Logging Settings During Runtime of Control Utilities

   • Using Log Files

   • Listener Log Audit Trail Information

   • Analyzing Oracle Connection Manager Logs

   Oracle Net Error Stacks

   Log files provide information contained in an error stack. An error stack refers to the information that is produced by each layer in an Oracle communications stack as the result of a network error.

   The error stack components are described in Table 16-2.

   Table 16-2 Error Stack Components

   Error Stack Component	Description
   NI	Network Interface. This layer provides a generic interface for Oracle clients, servers, or external processes to access Oracle Net functions. The NI layer handles the "break" and "reset" requests for a connection. NI uses the Network Routing (NR) layer to obtain network route information for pre-Oracle9i clients, and the Network Naming (NN) layer to resolve names to connect descriptors. For Oracle9i clients, NI goes directly to the Network Session (NS) layer.
   NS	Network Session (main and secondary layers). These layers receive requests from NI, and settle all generic computer-level connectivity issues, such as: the location of the server or destination (open, close functions); whether one or more protocols will be involved in the connection (open, close functions); and how to handle interrupts between client and server based on the capabilities of each (send, receive functions).
   NA	Network Authentication. This layer negotiates authentication and encryption requirements.
   NT	Network Transport (main, secondary, and operating system layers). This layer maps Oracle Net foundation layer functionality to industry-standard protocols.

   Example: Error Stack

   As an example, suppose that a user of a client application tries to establish a connection with a database server using Oracle Net and TCP/IP, and the user enters:

   sqlplus scott/[email protected]

   The following error displays:

   ORA-12543: TNS:Unable to connect to destination

   This message indicates that the connection to the server failed because the database could not be contacted. Although the application displays only a one-line error message, an error stack that is much more informative is recorded in the log file by the network layer.

   On the client side, the sqlnet.log file (Example 16-3) contains an error stack corresponding to the ORA-12543 error.

   Example 16-3 sqlnet.log File

   ***********************************************************

   Fatal OSN connect error 12543, connecting to: (DESCRIPTION=(CONNECT_DATA=(SID=trace)(CID=(PROGRAM=) (HOST=lala)(USER=sviavant)))(ADDRESS_LIST=(ADDRESS= (PROTOCOL=ipc)(KEY=trace))(ADDRESS=(PROTOCOL=tcp) (HOST=lala)(PORT=1521)))) VERSION INFORMATION: TNS for SunOS: Oracle Bequeath NT Protocol Adapter for SunOS: Unix Domain Socket IPC NT Protocol Adaptor for SunOS: TCP/IP NT Protocol Adapter for SunOS: Tracing to file: /home/sviavant/trace_admin.trc Tns error struct: TNS-12543: TNS:unable to connect to destination ns main err code: 12541 TNS-12541: TNS:no listener ns secondary err code: 12560 nt main err code: 511 TNS-00511: No listener nt secondary err code: 61 nt OS err code: 0

   Oracle Net Services Log File Names

   Each Oracle Net Services component produces its own log file. Table 16-3 provides the default log file names and lists the components that generate the log files.

   Table 16-3 Log Files

   Log File	Component
   listener.log	Listener
   sqlnet.log	Client or Database Server
   instance-name_pid.log	Oracle Connection Manager listener
   instance-name_cmgw_pid.log	Oracle Connection Manager CMGW (Connection Manager gateway) process
   instance-name_cmadmin_pid.log	Oracle Connection Manager CMADMIN (Connection Manager Administration) process
   instance-name_alert.log	Oracle Connection Manager alert log

   Setting Logging Parameters

   Parameters that control logging, including the type and amount of information logged, as well as the location where the files are stored, are set in the configuration file of each network component as described in Table 16-4.

   Table 16-4 Location of Log Parameters

   Network Component	Configuration File
   Oracle Connection Manager Processes	cman.ora
   Listener	listener.ora
   Client	sqlnet.ora
   Database Server	sqlnet.ora

   This section contains these topics:

   • sqlnet.ora Log Parameters

   • listener.ora Log Parameters

   • cman.ora Log Parameters

   • Setting Logging Parameters in Configuration Files

     See Also:

     Oracle Database Net Services Reference for more information about these parameters

   sqlnet.ora Log Parameters

   Table 16-5 describes the log parameters settings that can be set in the sqlnet.ora file.

   Table 16-5 sqlnet.ora Log Parameters

   sqlnet.ora Parameter	Oracle Net Manager Field	Description
   LOG_DIRECTORY_CLIENT	Client Information: Log Directory	Establishes the destination directory for the client log file. By default, the client directory is the current working directory.
   LOG_FILE_CLIENT	Client Information: Log File	Sets the name of the log file for the client. By default the log name is sqlnet.log.
   LOG_DIRECTORY_SERVER	Server Information: Log Directory	Establishes the destination directory for the database server log files. By default the server directory is $ORACLE_HOME/network/log on UNIX and ORACLE_HOME\network\log on Windows.
   LOG_FILE_SERVER	Not applicable	Sets the name of the log file for the database server. By default the log name is sqlnet.log.

   listener.ora Log Parameters

   Table 16-6 describes the log parameters settings that can be set in the listener.ora file.

   Table 16-6 listener.ora Log Parameters

   listener.ora Parameter	Oracle Enterprise Manager/Oracle Net Manager Field	Description
   LOG_DIRECTORY_listener_name and LOG_FILE_listener_name	Log File	Establishes the destination directory and file for the log file that is automatically generated for listener events. By default the directory is $ORACLE_HOME/network/log on UNIX and ORACLE_HOME\network\log on Windows, and the file name is defaulted to listener.log.

   cman.ora Log Parameters

   Table 16-7 describes the log parameters settings that can be set in the cman.ora file.

   Table 16-7 cman.ora Log Parameters

   cman.ora Parameter	Description
   EVENT_GROUP	Specifies which event groups are logged. Multiple events may be designated using a comma-separated list. This parameter accepts the following values: INIT_AND_TERM—initialization and termination MEMORY_OPS—memory operations CONN_HDLG—connection handling PROC_MGMT—process management REG_AND_LOAD—registration and load update WAKE_UP—events related to CMADMIN wakeup queue TIMER—gateway time outs CMD_PROC—command processing RELAY—events associated with connection control blocks
   LOG_DIRECTORY	Establishes the destination directory for log files. By default, the directory is $ORACLE_HOME/network/log on UNIX and ORACLE_HOME\network\log on Windows.
   LOG_LEVEL	Establishes the level of logging. Four levels are supported: off (default)—no logging user—user log information admin—administrative log information support—Oracle Support Services information The Oracle Connection Manager listener, gateway, and CMADMIN processes create log files on both UNIX and Windows.

   Setting Logging Parameters in Configuration Files

   You configure logging parameters for the sqlnet.ora file with Oracle Net Manager and listener.ora file with either Oracle Enterprise Manager or Oracle Net Manager.

   You must manually configure cman.ora file logging parameters.

   See Also:

   Oracle Database Net Services Reference

   To set logging parameters with Oracle Enterprise Manager and Oracle Net Manager:

   Log File	Tool	Set logging parameters here...
   sqlnet.log	Oracle Net Manager	Start Oracle Net Manager. See Also: "Oracle Net Manager" In the navigator pane, expand Local > Profile. From the list in the right pane, select General. Click the Logging tab. Specify the settings. Choose File > Save Network Configuration.
   listener.log	Oracle Enterprise Manager	Access the Oracle Net Administration page in Oracle Enterprise Manager. See Also: "Oracle Enterprise Manager" Select Listeners from the Administer list, and then select the Oracle home that contains the location of the configuration files. Click Go. The Listeners page appears. Select a listener, and then click Edit. The Edit Listeners page appears. Click the Logging & Tracing tab. Specify the settings. Click OK.
   listener.log	Oracle Net Manager	Start Oracle Net Manager. See Also: "Oracle Net Manager" In the navigator pane, expand Local > Listeners. Select a listener. From the list in the right pane, select General. Click the Logging and Tracing tab. Specify the settings. Choose File > Save Network Configuration.

   Setting Logging Settings During Runtime of Control Utilities

   You can set logging during control utility runtime. Setting logging with a control utility does not set parameters in the *.ORA files; the setting is only valid for the session of the control utility:

   • For a listener, use the SET LOG_FILE and SET LOG_DIRECTORY commands from the Listener Control utility.

   • For an Oracle Connection Manager, use the SET LOG_DIRECTORY, SET LOG_LEVEL, and SET EVENT commands from the Oracle Connection Manager control utility.

     See Also:

     Oracle Database Net Services Reference

   Using Log Files

   To use a log file to diagnose a network error:

   1. Review the log file for the most recent error number you received from the application. Note that this is almost always the last entry in the log file.

   2. Starting from the bottom of the file, locate the first nonzero entry in the error report. This is usually the actual cause.

   3. If that error does not provide the desired information, review the next error in the stack until you locate the correct error information.

   4. If the cause of the error is still not clear, turn on tracing and repeat the statement that produced the error message.

   Analyzing Listener Log Files

   This section describes what is recorded in the listener log file, including:

   • Listener Log Audit Trail Information

   • Listener Service Registration Event Information

   • Listener Direct Hand-Off Information

   Listener Log Audit Trail Information

   The listener log file contains audit trail information that enables you to gather and analyze network usage statistics, as well as information indicating the following:

   • A client connection request

   • A RELOAD, START, STOP, STATUS, or SERVICES command issued by the Listener Control utility

   You can use Audit Trail information to view trends and user activity by first storing it in a table and then collating it into a report format. To import the data into a table, use an import utility such as SQL*Loader.

   Format of the Listener Log Audit Trail

   The audit trail formats text into the following fields:

   Timestamp * Connect Data [* Protocol Info] * Event [* SID | Service] * Return Code

   Properties of the audit trail are as follows:

   • Each field is delimited by an asterisk (*).

   • Protocol address information and service name or SID information appear only when a connection is attempted.

   • A successful connection or command returns a code of zero.

   • A failure produces a code that maps to an error message.

     See Also:

     • "Resolving the Most Common Error Messages for Oracle Net Services" for information about resolving the most common Oracle Net errors

     • Oracle Database Error Messages for a complete listing of error messages

   Example: Listener Log Event for Successful Reload Request

   The following output shows a log file excerpt with RELOAD command request.

   14-JUL-2002 00:29:54 * (connect_data=(cid=(program=)(host=sales-server)(user=jdoe))(command=stop) (arguments=64)(service=listener)(version=135290880)) * stop * 0

   Example: Listener Log Events for a Successful Connection Request

   The following output shows a log file excerpt with a successful connection request.

   14-JUL-2002 15:28:58 * (connect_data=(service_name=sales.us.acme.com)(cid=(program=)(host=sales-server) (user=jdoe))) * (address=(protocol=tcp)(host=10.10.150.35)(port=41349)) * establish * sales.us.acme.com * 0

   Example: Listener Log Events for an Unsuccessful Connection Request

   The following output shows a log file excerpt with a successful execution of the STATUS command by host sales-server, followed by an unsuccessful connection attempt by a client with an IP address of 10.10.150.35. This connection attempt resulted in an ORA-12525: TNS:listener has not received client's request in time allowed error message, which occurs when a client fails to complete its connect request in the time specified by the INBOUND_CONNECT_TIMEOUT_listener_name parameter in the listener.ora file. This client may be attempting a denial-of-service attack on the listener.

   03-JUL-2002 16:41:57 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=sales-server)(USER=jdoe))(COMMAND=status) (ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=153092352)) * status * 0 03-JUL-2002 16:42:35 * <unknown connect data> * (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.150.35)(PORT=53208)) * establish * <unknown sid> * 12525 TNS-12525: TNS:listener has not received client's request in time allowed TNS-12604: TNS: Application timeout occurred

   Listener Service Registration Event Information

   The listener records service registration events. During service registration, the PMON process provides the listener with information about the following:

   • Service names for each running instance of the database

   • Instance names of the database

   • Service handlers (dispatchers or dedicated servers) available

   • Dispatcher, instance, and node load information

   • Dynamic listening endpoints

   The service registration-related events listed in Table 16-8 are recorded in the listener.log file:

   Table 16-8 Service Registration Event Log Information

   Event	Description
   service_register	The listener received registration information for an instance.
   service_update	The listener received updated registration information for a particular instance, such as dispatcher or instance load information.
   service_died	The listener lost its connection to PMON. All registration information for the instance is discarded. Clients will be unable to connect to the instance until PMON registers it again.

   Format of the Listener Service Registration Information

   The service registration events are formatted into the following fields:

   Timestamp * Event * Instance Name * Return Code

   Properties of service registration fields are as follows:

   • Each field is delimited by an asterisk (*).

   • It is normal for the events to appear multiple times in a row for one instance.

   • A successful registration returns a code of zero, meaning the client can connect to the instance.

   • A failure produces a code that maps to an error message.

     See Also:

     • "Resolving the Most Common Error Messages for Oracle Net Services" for the most common Oracle Net errors

     • Oracle Database Error Messages for a complete listing of error messages

   Example: Listener Log with Service Registration Events

   The following example shows a log file with service registration events. Notice how the listener is able to receive a client request after a successful service_register event, but is unable to receive client requests after a service_died event.

   ------------------------------- 14-JUL-2002 15:28:43 * service_register * sales * 0 14-JUL-2002 15:28:43 * service_register * sales * 0 14-JUL-2002 15:28:58 * (connect_data=(service_name=sales.us.acme.com)(cid=(program=)(host=sales-server) (user=jdoe))) * (address=(protocol=tcp)(host=10.10.150.35)(port=41349)) * establish * sales.us.acme.com * 0 14-JUL-2002 15:38:44 * service_update * sales * 0 14-JUL-2002 15:38:44 * service_update * sales * 0 14-JUL-2002 15:48:45 * service_update * sales * 0 14-JUL-2002 15:48:45 * service_update * sales * 0 14-JUL-2002 15:50:57 * (connect_data=(service_name=sales.us.acme.com)(cid=(program=)(host=sales-server)(u ser=jdoe))) * (address=(protocol=tcp)(host=10.10.150.35)(port=41365)) * establish * sales.us.acme.com * 0 14-JUL-2002 15:51:26 * service_died * sales * 12537 14-JUL-2002 15:51:26 * service_died * sales * 12537 14-JUL-2002 15:52:06 * (connect_data=(service_name=sales.us.acme.com)(cid=(program=)(host=sales-server)(u ser=jdoe))) * (address=(protocol=tcp)(host=10.10.150.35)(port=41406)) * establish * sales.us.acme.com * 12514 TNS-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor --------------------------------

   Listener Direct Hand-Off Information

   The listener records direct hand-off events to dispatchers. These events are formatted into the following fields:

   Timestamp * Presentation * Handoff * Error Code

   Properties of direct hand-off fields are as follows:

   • Each field is delimited by an asterisk (*).

   • A successful connection or command returns a code of zero.

   • A failure produces a code that maps to an error message.

     See Also:

     "Resolving the Most Common Error Messages for Oracle Net Services" for the most common Oracle Net errors or Oracle Database Error Messages for a complete listing of error messages

   Example: Listener Log Event for Direct Hand-Off

   A direct hand-off event in the log file is shown in the following example.

   21-JUL-2002 10:54:55 * oracle.aurora.net.SALESHttp2 * handoff * 0

   Listener Subscription for ONS Node Down Event Information

   Listener will subscribe to the Oracle Notification Service (ONS) node down event on startup if ONS configuration file is available. This subscription enables the listener to remove the affected service when it receives node down event notification from ONS. The listener uses asynchronous subscription for the event notification. The following warning message will be recorded to listener log file on each STATUS command if the subscription has not completed; for example if the ONS daemon is not running on the host.

   WARNING: Subscription for node down event still pending

   Listener will not be able to receive the ONS event while subscription is pending. Other than that, no other listener functionality is affected.

   Listener CRS Notification Information

   If the required CRS (Cluster Ready Services) libraries are installed and CRS is started on the host, Listener will notify CRS about its status upon start and stop. After successful notification, listeners records the event in the log. No message will be recorded if the notification fails.

   Listener completed notification to CRS on start Listener completed notification to CRS on stop

   Analyzing Oracle Connection Manager Logs

   Oracle Connection Manager generates four types of log files: one each for its listener, gateway, and CMADMIN processes and one for alerts. The last is a chronological record of all critical errors. In addition to logging critical errors, the alert log captures information about instance startup and shutdown. It also records the value of all configuration parameters at the beginning and end of a session. See Table 16-3 for file name syntax.

   The CMADMIN and gateway log files are reproduced here. Table 16-9 explains some of the log entries. Each entry consists of a timestamp and an event. You can configure cman.ora to log events in the following categories:

   • Initialization and termination

   • Memory operations

   • Connection handling

   • Process management

   • Registration and load update

   • Events related to CMADMIN wakeup queue

   • Gateway timeouts

   • Command processing

   • Events associated with connection control blocks

   Use the SET EVENT command to specify which events to log.

   CMADMIN Log File Example

   ------------------------------- (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:40)(EVENT=Parameter list) (listener_address=(address=(protocol=tcp)(host=usunnae16)(port=1574))) (aso_authentication_filter=OFF) (connection_statistics=ON) (log_directory=/home/user/network/admin/log) (log_level=support) (max_connections=256) (idle_timeout=5) (inbound_connect_timeout=0) (session_timeout=20) (outbound_connect_timeout=0) (max_gateway_processes=1) (min_gateway_processes=1) (password=OFF) (remote_admin=ON) (trace_directory=/home/user/network/admin/log) (trace_level=off) (trace_timestamp=OFF) (trace_filelen=0) (trace_fileno=0) ) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:40)(EVENT=Shared Memory Size) (BYTES=82524)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:40)(EVENT=GMON Attributes validated) (Type=Information)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:40)(EVENT=NS Listen Successful) ((ADDRESS=(PROTOCOL=tcp)(HOST=usunnae16)(PORT=55878)))) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:44)(EVENT=Received command)(CMD=verify password)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:44)(EVENT=Received command) (CMD=version)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:44)(EVENT=Received command) (CMD=show status)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:44)(EVENT=Failed to get procedure id)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:49:12)(EVENT=Received command)(CMD=verify password)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:49:15)(EVENT=Failed to get procedure id)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:49:29)(EVENT=Received command)(CMD=verify password)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:49:46)(EVENT=Failed to get procedure id)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:49:50)(EVENT=Received command)(CMD=verify password)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:49:50)(EVENT=Received command) (CMD=probe monitor)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:49:50)(EVENT=Received command) (CMD=shutdown normal)) -------------------------------

   Gateway Log File Example

   ------------------------------- (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:41)(EVENT=NS Initialised)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:41)(EVENT=Memory Allocated) (BYTES=1024)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:41)(EVENT=NCR Initialised)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:41)(EVENT=Connected to Monitor)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:41)(EVENT=State Change from Empty to Init)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:41)(EVENT=Memory Allocated) (BYTES=251904)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:41)(EVENT=Memory Allocated) (BYTES=2048)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:41)(EVENT=CCB Initialised)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:41)(EVENT=Started Listening)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:41)(EVENT=State Change from Init to Ready)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:46:47)(EVENT=Housekeeping)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:06)(EVENT=Ready)(CONN NO=0)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:06)(EVENT=Ready)(CONN NO=0)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:07)(EVENT=Housekeeping)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:12)(EVENT=Housekeeping)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:13)(EVENT=Idle Timeout)(CONN NO=0)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:17)(EVENT=Housekeeping)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:22)(EVENT=Housekeeping)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:25)(EVENT=Ready)(CONN NO=0)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:25)(EVENT=Ready)(CONN NO=0)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:27)(EVENT=Housekeeping)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:30)(EVENT=Idle Timeout)(CONN NO=0)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:32)(EVENT=Housekeeping)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:37)(EVENT=Housekeeping)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:42)(EVENT=Ready)(CONN NO=0)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:42)(EVENT=Ready)(CONN NO=0)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:42)(EVENT=Housekeeping)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:47)(EVENT=Housekeeping)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:52)(EVENT=Housekeeping)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:48:57)(EVENT=Housekeeping)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:49:02)(EVENT=Session Timeout)(CONN NO=0)) (LOG_RECORD=(TIMESTAMP=08-MAY-2003 08:49:02)(EVENT=Housekeeping)) -------------------------------

   Table 16-9 CMADMIN and Gateway Log Entries: What They Mean

   Event	Description	Log File
   GMON Attributes validated	Informational message. The parameters needed for CMADMIN to come up are specified correctly.	CMADMIN
   Failed to get procedure ID	The CMCTL session connected to CMADMIN has disconnected.	CMADMIN
   Out of CCB	CMADMIN is unable to process a connection request. There could be two reasons: Faulty load update between CMADMIN and listener Someone is trying to connect to CMADMIN directly (possibly a denial of service attack)	Gateway
   No connect data	An unknown client is trying to connect to CMADMIN. This is most likely a denial of service attack.	CMADMIN
   Invalid connect data	An unknown client is trying to connect to CMADMIN. This is most likely a denial of service attack.	CMADMIN
   Housekeeping	Informational message. Internal housekeeping for the gateway process is in order. The gateway process is properly connected to the CMADMIN process.	Gateway
   Connected to Monitor	The gateway has connected to CMADMIN.	Gateway
   State change from Empty to Init	State change message from the gateway. Once it reaches a ready state, the gateway begins accepting connections from the client.	Gateway
   State change from Init to Ready	State change message from the gateway. Once it reaches a ready state, the gateway begins accepting connections from the client.	Gateway
   Idle Timeout	The connection was disconnected because it was idle longer than the time specified in cman.ora.	Gateway
   Session Timeout	The connection was disconnected because it exceeded the session timeout specified in cman.ora.	Gateway

   Tracing Error Information for Oracle Net Services

   Tracing produces a detailed sequence of statements that describe network events as they are executed. Tracing an operation enables you to obtain more information on the internal operations of the components of Oracle Net Services than is provided in a log file. This information is output to files that can be evaluated to identify the events that led to an error.

   CAUTION:

   Tracing uses a large amount of disk space and may have a significant impact upon system performance. Therefore, you should enable tracing only when necessary.

   This section contains topics:

   • Oracle Net Services Trace File Names

   • Setting Tracing Parameters

   • Setting Tracing Settings During Runtime of Control Utilities

   • Evaluating Oracle Net Services Traces

   • Using the Trace Assistant to Examine Trace Files

   Oracle Net Services Trace File Names

   Each Oracle Net Services component produces its own trace file. Table 16-10 provides the default trace file names and lists the components that generate the trace files.

   Table 16-10 Trace Files

   Trace File	Component
   instance-name_pid.trc	Oracle Connection Manager listener
   instance-name_cmgw_pid.trc	Oracle Connection Manager CMGW (Connection Manager gateway) process
   instance-name_cmadmin_pid.trc	Oracle Connection Manager CMADMIN (Connection Manager Administration) process
   listener.trc	Listener
   sqlnet.trc	Client
   svr_pid.trc	Database Server
   tnsping.trc	TNSPING Utility

   Setting Tracing Parameters

   Parameters that control tracing, including the type and amount of information trace, as well as the location where the files are stored, are set in the configuration file of each network component as described in Table 16-11.

   Table 16-11 Location of Trace Parameters

   Component	Configuration File
   Oracle Connection Manager Processes	cman.ora
   Listener	listener.ora
   Client	sqlnet.ora
   Database Server	sqlnet.ora
   TNSPING Utility	sqlnet.ora

   This section contains these topics:

   • sqlnet.ora Trace Parameters

   • listener.ora Trace Parameters

   • cman.ora Trace Parameters

   • Setting Tracing Parameters in Configuration Files

     See Also:

     Oracle Database Net Services Reference for more information about these parameters

   sqlnet.ora Trace Parameters

   Table 16-12 describes the trace parameters settings that can be set in the sqlnet.ora file.

   Table 16-12 sqlnet.ora Trace Parameters

   sqlnet.ora Parameter	Oracle Net Manager Field	Description
   TRACE_DIRECTORY_CLIENT	Client Information: Trace Directory	Establishes the destination directory for the client trace output. By default, the client directory is $ORACLE_HOME/network/trace on UNIX and ORACLE_HOME\network\trace on Windows.
   TRACE_DIRECTORY_SERVER	Server Information: Trace Directory	Establishes the destination directory for the database server trace output. By default, the server directory is $ORACLE_HOME/network/trace on UNIX and ORACLE_HOME\network\trace on Windows.
   TRACE_FILE_CLIENT	Client Information: Trace File	Sets the name of the trace file for the client. By default the trace file name is sqlnet.trc.
   TRACE_FILE_SERVER	Server Information: Trace File	Sets the name of the trace file for the database server. By default the trace file name is svr_pid.trc.
   TRACE_FILELEN_CLIENT	Not Applicable	Specifies the size of the client trace files in kilobytes (KB). When the size is met, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_CLIENT parameter.
   TRACE_FILELEN_SERVER	Not Applicable	Specifies the size of the database server trace files in kilobytes (KB). When the size is met, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_CLIENT parameter.
   TRACE_FILENO_CLIENT	Not Applicable	Specifies the number of trace files for client tracing. When this parameter is set along with the TRACE_FILELEN_CLIENT parameter, trace files are used in a cyclical fashion. The first file is filled first, then the second file, and so on. When the last file has been filled, the first file is re-used, and so on. The trace file names are distinguished from one another by their sequence number. For example, if the default trace file of sqlnet.trc is used, and this parameter is set to 3, the trace files would be named sqlnet1_pid.trc, sqlnet2_pid.trc and sqlnet3_pid.trc. In addition, trace events in the trace files are preceded by the sequence number of the file.
   TRACE_FILENO_SERVER	Not Applicable	Specifies the number of trace files for database server tracing. When this parameter is set along with the TRACE_FILELEN_SERVER parameter, trace files are used in a cyclical fashion. The first file is filled first, then the second file, and so on. When the last file has been filled, the first file is re-used, and so on. The trace file names are distinguished from one another by their sequence number. For example, if the default trace file of svr_pid.trc is used, and this parameter is set to 3, the trace files would be named svr1_pid.trc, svr2_pid.trc and svr3_pid.trc. In addition, trace events in the trace files are preceded by the sequence number of the file.
   TRACE_LEVEL_CLIENT	Client Information: Trace Level	Specifies the level of detail the trace facility records for the client. The trace level value can either be a value within the range of 0 (zero) to 16 (where 0 is no tracing and 16 represents the maximum amount of tracing) or a value of off, admin, user, or support. off (equivalent to 0) provides no tracing user (equivalent to 4) traces to identify user-induced error conditions admin (equivalent to 6) traces to identify installation-specific problems support (equivalent to 16) provides trace information for troubleshooting information for Oracle Support Services
   TRACE_LEVEL_SERVER	Server Information: Trace Level	Specifies the level of detail the trace facility records for the database server. The trace level value can either be a value within the range of 0 (zero) to 16 (where 0 is no tracing and 16 represents the maximum amount of tracing) or a value of off, admin, user, or support. off (equivalent to 0) provides no tracing user (equivalent to 4) traces to identify user-induced error conditions admin (equivalent to 6) traces to identify installation-specific problems support (equivalent to 16) provides trace information for troubleshooting information for Oracle Support Services
   TRACE_TIMESTAMP_CLIENT	Not Applicable	Adds a time stamp in the form of dd-mon-yyyy hh:mi:ss:mil to every trace event in the client trace file, sqlnet.trc.
   TRACE_TIMESTAMP_SERVER	Not Applicable	Adds a time stamp in the form of dd-mon-yyyy hh:mi:ss:mil to every trace event in the client trace file, sqlnet.trc.
   TRACE_UNIQUE_CLIENT	Client Information: Unique Trace File Name	When the value is set to on, Oracle Net creates a unique file name for each trace session by appending a process identifier to the name of each trace file generated, enabling several files to coexist. For example, trace files named sqlnetpid.trc are created if default trace file name sqlnet.trc is used. When the value is set to off, data from a new client trace session overwrites the existing file.

   You can manually add the following TNSPING utility tracing parameters described in Table 16-13 to sqlnet.ora. The TNSPING utility determines whether or not a service (such as a databaseor other TNS services) on a Oracle Net network can be successfully reached.

   Table 16-13 TNSPING Trace Parameters

   sqlnet.ora Parameter	Description
   TNSPING.TRACE_DIRECTORY	Establishes the destination directory for TNSPING trace file, tnsping.trc. By default, the directory is $ORACLE_HOME/network/trace on UNIX and ORACLE_HOME\network\trace on Windows.
   TNSPING.TRACE_LEVEL	Specifies the level of detail the trace facility records for the TNSPING utility. The trace level value can either be a value within the range of 0 (zero) to 16 (where 0 is no tracing and 16 represents the maximum amount of tracing) or a value of off, admin, user, or support. off (equivalent to 0) provides no tracing user (equivalent to 4) traces to identify user-induced error conditions admin (equivalent to 6) traces to identify installation-specific problems support (equivalent to 16) provides trace information for troubleshooting information for Oracle Support Services

   listener.ora Trace Parameters

   Table 16-14 describes the trace parameters settings for the listener that can be set in the listener.ora file.

   Table 16-14 listener.ora Trace Parameters

   listener.ora Parameter	Oracle Enterprise Manager/Oracle Net Manager Field	Description
   TRACE_LEVEL_listener_name	Select a trace level/Trace Level	Specifies the level of detail the trace facility records for the listener. The trace level value can either be a value within the range of 0 (zero) to 16 (where 0 is no tracing and 16 represents the maximum amount of tracing) or a value of off, admin, user, or support. off (equivalent to 0) provides no tracing user (equivalent to 4) traces to identify user-induced error conditions admin (equivalent to 6) traces to identify installation-specific problems support (equivalent to 16) provides trace information for troubleshooting information for Oracle Support Services
   TRACE_DIRECTORY_listener_name TRACE_FILE_listener_name	Trace File	Establishes the destination directory and file for the trace file. By default the directory is $ORACLE_HOME/network/trace on UNIX and ORACLE_HOME\network\trace on Windows, and the file name is listener.trc.
   TRACE_FILELEN_listener_name	Not Applicable	Specifies the size of the listener trace files in kilobytes (KB). When the size is met, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_listener_name parameter
   TRACE_FILENO_listener_name	Not Applicable	Specifies the number of trace files for listener tracing. When this parameter is set along with the TRACE_FILELEN_listener_name parameter, trace files are used in a cyclical fashion. The first file is filled first, then the second file, and so on. When the last file has been filled, the first file is re-used, and so on. The trace file names are distinguished from one another by their sequence number. For example, if the default trace file of listener.trc is used, and this parameter is set to 3, the trace files would be named listener1.trc, listener2.trc and listener3.trc. In addition, trace events in the trace files are preceded by the sequence number of the file.
   TRACE_TIMESTAMP_listener_name	Not Applicable	Adds a time stamp in the form of dd-mon-yyyy hh:mi:ss:mil to every trace event in the listener trace file.

   cman.ora Trace Parameters

   Table 16-15 describes the trace parameters settings for Oracle Connection Manager that can be set in the cman.ora file.

   Table 16-15 cman.ora Trace Parameters

   cman.ora Parameter	Description
   TRACE_DIRECTORY	Establishes the destination directory for trace files. By default, the directory is $ORACLE_HOME/network/trace on UNIX and ORACLE_HOME\network\trace on Windows.
   TRACE_FILELEN	Specifies the size of the trace file in kilobytes (KB). When the size is met, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO parameter.
   TRACE_FILENO	Specifies the number of trace files for tracing. When this parameter is set along with the TRACE_FILELEN parameter, trace files are used in a cyclical fashion. The first file is filled first, then the second file, and so on. When the last file has been filled, the first file is reused, and so on. The trace file names are distinguished from one another by their sequence number. For example, if this parameter is set to 3, the Oracle Connection Manager trace files for the gateway processes would be named instance-name_cmgw1_pid.trc, instance-name_cmgw2_pid.trc and instance-name_cmgw3_pid.trc. In addition, trace events in the trace files are preceded by the sequence number of the file.
   TRACE_LEVEL	Specifies the trace level for the Oracle Connection Manager instance. This parameter accepts four trace levels: off (default)—no logging user—user log information admin—administrative log information support—Oracle Support Services information The Oracle Connection Manager listener, gateway, and CMADMIN processes create trace files on both UNIX and Windows. See Table 16-10 for file name syntax.
   TRACE_TIMESTAMP	If the TRACING parameter is enabled, adds a time stamp in the form of dd-mon-yyyy hh:mi:ss:mil to every trace event in the trace files.

   Setting Tracing Parameters in Configuration Files

   You configure tracing parameters for the sqlnet.ora file with Oracle Net Manager and listener.ora file with either Oracle Enterprise Manager or Oracle Net Manager.

   You must manually configure cman.ora file tracing parameters.

   See Also:

   Oracle Database Net Services Reference

   To set tracing parameters with Oracle Enterprise Manager and Oracle Net Manager:

   Trace File	Tool	Set logging parameters here...
   sqlnet.trc (for the client) svr_pid.trc (for the server)	Oracle Net Manager	Start Oracle Net Manager. See Also: "Oracle Net Manager" In the navigator pane, expand Local > Profile. From the list in the right pane, select General. Click the Tracing tab. Specify the settings. Choose File > Save Network Configuration.
   listener.trc	Oracle Enterprise Manager	Access the Oracle Net Administration page in Oracle Enterprise Manager. See Also: "Oracle Enterprise Manager" Select Listeners from the Administer list, and then select the Oracle home that contains the location of the configuration files. Click Go. The Listeners page appears. Select a listener, and then click Edit. The Edit Listeners page appears. Click the Logging & Tracing tab. Specify the settings. Click OK.
   listener.trc	Oracle Net Manager	Start Oracle Net Manager. See Also: "Oracle Net Manager" In the navigator pane, expand Local > Listeners. Select a listener. From the list in the right pane, select General. Click the Logging and Tracing tab. Specify the settings. Choose File > Save Network Configuration.

   Setting Tracing Settings During Runtime of Control Utilities

   You can set tracing during control utility runtime. Setting tracing with a control utility does not set parameters in the *.ORA files; the setting is only valid for the session of the control utility:

   • For the listener, use the SET TRC_DIRECTORY, SET TRC_FILE, and SET TRC_LEVEL commands from the Listener Control utility.

   • For an Oracle Connection Manager, use the SET TRACE_DIRECTORY and SET TRACE_LEVEL, and SET TRACE_TIMESTAMP commands from the Oracle Connection Manager control utility.

     See Also:

     Oracle Database Net Services Reference

   Evaluating Oracle Net Services Traces

   Trace files can help Oracle Support Service diagnose and troubleshoot network problems.

   This section explains how to perform basic analysis of trace files. The topics discussed include:

   • Flow of Data Packets Between Network Nodes

   • Oracle Net Data Packet Formats

   • Pertinent Oracle Net Trace Error Output

   Flow of Data Packets Between Network Nodes

   Oracle Net performs its functions by sending and receiving data packets.By specifying a trace level of support, you can view the actual contents of the Oracle Net packet in your trace file. The order of the packet types sent and received will help you to determine how your connection was established.

   Oracle Net Data Packet Formats

   Each line in the trace file begins with a procedure followed by a message. Following each procedure is a line of hexadecimal data representing actual data. The actual data that flows inside the packet is sometimes viewable to the right of the hexadecimal data.

   Next is a list of the Oracle Net packet keywords and descriptions of the types of packets they represent:

   Keyword	Packet Type
   NSPTCN	Connect
   NSPTAC	Accept
   NSPTRF	Refuse
   NSPTRS	Resend
   NSPTDA	Data
   NSPCNL	Control
   NSPTMK	Marker

   Pertinent Oracle Net Trace Error Output

   When there is a problem a connection, the error code is logged in the trace file. Example 16-5 depicts typical trace file output for a failed SQL*Plus connection to a database server.

   Example 16-5 Trace Example

   [22-JUL-2002 13:34:07:687] nsprecv: entry [22-JUL-2002 13:34:07:687] nsbal: entry [22-JUL-2002 13:34:07:687] nsbgetfl: entry [22-JUL-2002 13:34:07:687] nsbgetfl: normal exit [22-JUL-2002 13:34:07:687] nsmal: entry [22-JUL-2002 13:34:07:687] nsmal: 44 bytes at 0x132d90 [22-JUL-2002 13:34:07:687] nsmal: normal exit [22-JUL-2002 13:34:07:687] nsbal: normal exit [22-JUL-2002 13:34:07:687] nsprecv: reading from transport... [22-JUL-2002 13:34:07:687] nttrd: entry [22-JUL-2002 13:35:09:625] nttrd: exit [22-JUL-2002 13:35:09:625] ntt2err: entry [22-JUL-2002 13:35:09:625] ntt2err: Read unexpected EOF ERROR on 10 [22-JUL-2002 13:35:09:625] ntt2err: exit [22-JUL-2002 13:35:09:625] nsprecv: transport read error [22-JUL-2002 13:35:09:625] nsprecv: error exit [22-JUL-2002 13:35:09:625] nserror: entry [22-JUL-2002 13:35:09:625] nserror: nsres: id=0, op=68, ns=12537, ns2=12560; nt[0]=507, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0 [22-JUL-2002 13:35:09:625] nscon: error exit [22-JUL-2002 13:35:09:625] nsdo: nsctxrnk=0 [22-JUL-2002 13:35:09:625] nsdo: error exit [22-JUL-2002 13:35:09:625] nscall: unexpected response [22-JUL-2002 13:35:09:625] nsclose: entry [22-JUL-2002 13:35:09:625] nstimarmed: entry [22-JUL-2002 13:35:09:625] nstimarmed: no timer allocated [22-JUL-2002 13:35:09:625] nstimarmed: normal exit [22-JUL-2002 13:35:09:625] nsdo: entry [22-JUL-2002 13:35:09:625] nsdo: cid=0, opcode=98, *bl=0, *what=0, uflgs=0x440, cflgs=0x2 [22-JUL-2002 13:35:09:625] nsdo: rank=64, nsctxrnk=0 [22-JUL-2002 13:35:09:625] nsdo: nsctx: state=1, flg=0x4201, mvd=0 [22-JUL-2002 13:35:09:625] nsbfr: entry [22-JUL-2002 13:35:09:625] nsbaddfl: entry [22-JUL-2002 13:35:09:625] nsbaddfl: normal exit [22-JUL-2002 13:35:09:625] nsbfr: normal exit [22-JUL-2002 13:35:09:625] nsbfr: entry [22-JUL-2002 13:35:09:625] nsbaddfl: entry [22-JUL-2002 13:35:09:625] nsbaddfl: normal exit [22-JUL-2002 13:35:09:625] nsbfr: normal exit [22-JUL-2002 13:35:09:625] nsdo: nsctxrnk=0 [22-JUL-2002 13:35:09:625] nsdo: normal exit [22-JUL-2002 13:35:09:625] nsclose: closing transport [22-JUL-2002 13:35:09:625] nttdisc: entry [22-JUL-2002 13:35:09:625] nttdisc: Closed socket 10 [22-JUL-2002 13:35:09:625] nttdisc: exit [22-JUL-2002 13:35:09:625] nsclose: global context check-out (from slot 0) complete [22-JUL-2002 13:35:09:703] nsnadisc: entry [22-JUL-2002 13:35:09:703] nadisc: entry [22-JUL-2002 13:35:09:703] nacomtm: entry [22-JUL-2002 13:35:09:703] nacompd: entry [22-JUL-2002 13:35:09:703] nacompd: exit [22-JUL-2002 13:35:09:703] nacompd: entry [22-JUL-2002 13:35:09:703] nacompd: exit [22-JUL-2002 13:35:09:703] nacomtm: exit [22-JUL-2002 13:35:09:703] nas_dis: entry [22-JUL-2002 13:35:09:703] nas_dis: exit [22-JUL-2002 13:35:09:703] nau_dis: entry [22-JUL-2002 13:35:09:703] nau_dis: exit [22-JUL-2002 13:35:09:703] naeetrm: entry [22-JUL-2002 13:35:09:703] naeetrm: exit [22-JUL-2002 13:35:09:703] naectrm: entry [22-JUL-2002 13:35:09:703] naectrm: exit [22-JUL-2002 13:35:09:703] nagbltrm: entry [22-JUL-2002 13:35:09:703] nau_gtm: entry [22-JUL-2002 13:35:09:703] nau_gtm: exit [22-JUL-2002 13:35:09:703] nagbltrm: exit [22-JUL-2002 13:35:09:703] nadisc: exit [22-JUL-2002 13:35:09:703] nsnadisc: normal exit [22-JUL-2002 13:35:09:703] nsbfr: entry [22-JUL-2002 13:35:09:703] nsbaddfl: entry [22-JUL-2002 13:35:09:703] nsbaddfl: normal exit [22-JUL-2002 13:35:09:703] nsbfr: normal exit [22-JUL-2002 13:35:09:703] nsmfr: entry [22-JUL-2002 13:35:09:703] nsmfr: 2256 bytes at 0x130508 [22-JUL-2002 13:35:09:703] nsmfr: normal exit [22-JUL-2002 13:35:09:703] nsmfr: entry [22-JUL-2002 13:35:09:703] nsmfr: 484 bytes at 0x1398a8 [22-JUL-2002 13:35:09:703] nsmfr: normal exit [22-JUL-2002 13:35:09:703] nsclose: normal exit [22-JUL-2002 13:35:09:703] nscall: connecting... [22-JUL-2002 13:35:09:703] nsclose: entry [22-JUL-2002 13:35:09:703] nsclose: normal exit [22-JUL-2002 13:35:09:703] nladget: entry [22-JUL-2002 13:35:09:734] nladget: exit [22-JUL-2002 13:35:09:734] nsmfr: entry [22-JUL-2002 13:35:09:734] nsmfr: 144 bytes at 0x132cf8 [22-JUL-2002 13:35:09:734] nsmfr: normal exit [22-JUL-2002 13:35:09:734] nsmfr: entry [22-JUL-2002 13:35:09:734] nsmfr: 156 bytes at 0x138e70 [22-JUL-2002 13:35:09:734] nsmfr: normal exit [22-JUL-2002 13:35:09:734] nladtrm: entry [22-JUL-2002 13:35:09:734] nladtrm: exit [22-JUL-2002 13:35:09:734] nscall: error exit [22-JUL-2002 13:35:09:734] nioqper: error from nscall [22-JUL-2002 13:35:09:734] nioqper: ns main err code: 12537 [22-JUL-2002 13:35:09:734] nioqper: ns (2) err code: 12560 [22-JUL-2002 13:35:09:734] nioqper: nt main err code: 507 [22-JUL-2002 13:35:09:734] nioqper: nt (2) err code: 0 [22-JUL-2002 13:35:09:734] nioqper: nt OS err code: 0 [22-JUL-2002 13:35:09:734] niomapnserror: entry [22-JUL-2002 13:35:09:734] niqme: entry [22-JUL-2002 13:35:09:734] niqme: reporting NS-12537 error as ORA-12537 [22-JUL-2002 13:35:09:734] niqme: exit [22-JUL-2002 13:35:09:734] niomapnserror: returning error 12537 [22-JUL-2002 13:35:09:734] niomapnserror: exit [22-JUL-2002 13:35:09:734] niotns: Couldn't connect, returning 12537 [22-JUL-2002 13:35:10:734] niotns: exit [22-JUL-2002 13:35:10:734] nsbfrfl: entry [22-JUL-2002 13:35:10:734] nsbrfr: entry [22-JUL-2002 13:35:10:734] nsbrfr: nsbfs at 0x132d90, data at 0x132dc8. [22-JUL-2002 13:35:10:734] nsbrfr: normal exit [22-JUL-2002 13:35:10:734] nsbrfr: entry [22-JUL-2002 13:35:10:734] nsbrfr: nsbfs at 0x1248d8, data at 0x132210. [22-JUL-2002 13:35:10:734] nsbrfr: normal exit [22-JUL-2002 13:35:10:734] nsbrfr: entry [22-JUL-2002 13:35:10:734] nsbrfr: nsbfs at 0x12d820, data at 0x1319f0. [22-JUL-2002 13:35:10:734] nsbrfr: normal exit [22-JUL-2002 13:35:10:734] nsbfrfl: normal exit [22-JUL-2002 13:35:10:734] nigtrm: Count in the NI global area is now 1 [22-JUL-2002 13:35:10:734] nigtrm: Count in the NL global area is now 1

   The most efficient way to evaluate error codes is to find the most recent nserror entry logged, as the session layer controls the connection. The most important error messages are the ones at the bottom of the file. They are the most recent errors and the source of the problem with the connection.

   For information about the specific return codes, use the Oracle UNIX error tool oerr, by entering the following at any command line:

   oerr tns error_number

   As an example, consider the following nserror entry logged in the trace file shown in Figure 16-0:

   [22-JUL-2002 13:35:09:625] nserror: nsres: id=0, op=68, ns=12537, ns2=12560; nt[0]=507, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0

   Using oerr, you can find out more information about return codes 12537 and 507. (Bold denotes user input.)

   oerr tns 12537 12537, 00000, "TNS:connection closed" // *Cause: "End of file" condition has been reached; partner has disconnected. // *Action: None needed; this is an information message. oerr tns 507 00507, 00000, "Connection closed" // *Cause: Normal "end of file" condition has been reached; partner has // disconnected. // *Action: None needed; this is an information message.

   Using the Trace Assistant to Examine Trace Files

   Oracle Net Services provides a tool called the Trace Assistant to help you understand the information provided in trace files by converting existing lines of trace file text into a more readable paragraph. Note that the Trace Assistant runs against only a level 16 (support) Oracle Net Services trace file.

   This section contains the following topics:

   • Trace Assistant Syntax

   • Packet Examples

   • Two-Task Common Packet Examples

   • Connection Example

   • Statistics Example

   Trace Assistant Syntax

   To run the Trace Assistant, enter the following at any command line prompt:

   trcasst [options] <filename>

   The options are described in Table 16-16.

   Table 16-16 Trace Assistant Syntax

   Option	Description
   -elevel	Displays error information. After the -e, zero or one error decoding level may follow: 0 or nothing translates the NS error numbers dumped from the nserror function plus lists all other errors 1 displays only the NS error translation from the nserror function 2 displays error numbers without translation
   -la	If a connection ID exists in the NS connect packet, then the output displays the connection IDs. Connection IDs are displayed as hexadecimal, eight-byte IDs. A generated ID is created by Trace Assistant if the packet is not associated with any connection, that is, the connect packet is overwritten in the trace file. This can occur with cyclic trace files. For each ID, the output lists the following: Socket ID, if the connection has one Connect packet send or receive operation Current setting of the MULTIPLEX attribute of the DISPATCHERS parameter in the initialization parameter file. When MULTIPLEX is set to ON, session multiplexing is enabled. Session ID, if MULTIPLEX is set to ON Connect data information Notes: Do not use this option with other options. The IDs generated by the Trace Assistant do not correlate with client/server trace files.
   -li ID	Displays the trace for a particular ID from the -la output Note: Only use this option with output from the -la option.
   -otype	Displays the amount and type of information to be output. After the -o the following options can be used: c to display summary connectivity information d to display detailed connectivity information u to display summary Two-Task Common (TTC) information t to display detailed TTC information q to display SQL commands enhancing summary TTC information. Use this option with u, such as -ouq. Note: As output for d contains the same information as displayed for c, do not submit both c and d. If you submit both, then only output d will be processed.
   -p	Oracle internal use only
   -s	Displays the following statistical information: Total number of bytes sent and received Maximum open cursors Currently open cursors Count and ratio of operations Parsing and execution count for PL/SQL Total calls sent and received Total, average, and maximum number of bytes sent and received Total number of transports and sessions present Timestamp information, if any Sequence numbers, if any

   If no options are provided, then the default is -odt -e0 -s, providing detailed connectivity and TTC events, error level zero (0), and statistics in the trace file.

   Example 16-6 shows how the Trace Assistant converts trace file information into a more readable format.

   Example 16-6 Trace File with Error

   ntus2err: exit ntuscni: exit ntusconn: exit nserror: entry -<ERROR>- nserror: nsres: id=0, op=65, ns=12541, ns2=12560; nt[0]=511, nt[1]=2, nt[2]=0

   Example 16-7 shows how the Trace Assistant converts the trace file information into a more readable format with the -e1 option.

   Example 16-7 trcasst -e1 Output

   ************************************************************************* * Trace Assistant * ************************************************************************* ntus2err: exit ntuscni: exit ntusconn: exit nserror: entry -<ERROR>- nserror: nsres: id=0, op=65, ns=12541, ns2=12560; nt[0]=511, nt[1]=2, nt[2]=0 /////////////////////////////////////////////////////////////// Error found. Error Stack follows: id:0 Operation code:65 NS Error 1:12541 NS Error 2:12560 NT Generic Error:511 Protocol Error:2 OS Error:0 NS & NT Errors Translation 12541, 00000 "TNS:no listener" // *Cause: The connection request could not be completed because the listener // is not running. // *Action: Ensure that the supplied destination address matches one of // the addresses used by the listener - compare the TNSNAMES.ORA entry with // the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to // go by way of an Interchange). Start the listener on the remote machine. / 12560, 00000 "TNS:protocol adapter error" // *Cause: A generic protocol adapter error occurred. // *Action: Check addresses used for proper protocol specification. Before // reporting this error, look at the error stack and check for lower level // transport errors.For further details, turn on tracing and reexecute the // operation. Turn off tracing when the operation is complete. / 00511, 00000 "No listener" // *Cause: The connect request could not be completed because no application // is listening on the address specified, or the application is unable to // service the connect request in a sufficiently timely manner. // *Action: Ensure that the supplied destination address matches one of // the addresses used by the listener - compare the TNSNAMES.ORA entry with // appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go // by way of an Interchange. Start the listener on the remote machine. / /////////////////////////////////////////////////////////////// ************************************************************************* * Trace Assistant has completed * *************************************************************************

   However, other errors may also exist within the trace file that were not logged from the nserror function.

   Packet Examples

   Trace Assistant also enables you to view data packets from both the Oracle Net and TTC communication layers. Trace Assistant offers you two options to view these packets:

   • Summary connectivity (using option -oc)

   • Detailed connectivity (using option -od)

   Example: Summary Data Packets Sent in a Connection

   Example 16-8 shows summary information from the -oc option. The output shows....

   Example 16-8 trcasst -oc Output

   ************************************************************************* * Trace Assistant * ************************************************************************* ---> Send 198 bytes - Connect packet Connect data length: 140 Connect Data: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=sales-server)(PORT=1521)) (CONNECT_DATA=(SERVICE_NAME=sales.us.acme.com)(CID=(PROGRAM=) (HOST=sales-server)(USER=joe)))) <--- Received 76 bytes - Redirect packet Redirect data length: 66 Redirect Data: (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521)) ---> Send 198 bytes - Connect packet Connect data length: 140 Connect Data: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=sales-server)(PORT=1521)) (CONNECT_DATA=(SERVICE_NAME=sales.us.acme.com)(CID=(PROGRAM=) (HOST=sales-server)(USER=joe)))) <--- Received 32 bytes - Accept packet Connect data length: 0 ---> Send 153 bytes - Data packet Native Services negotiation packet <--- Received 127 bytes - Data packet Native Services negotiation packet ---> Send 32 bytes - Data packet <--- Received 140 bytes - Data packet ************************************************************************* * Trace Assistant has completed * *************************************************************************

   Note that the packets being sent or received have a prefix of "---> Send nnn bytes" or "<--- Received nnn bytes" showing that this node is sending or receiving a packet of a certain type and with nnn number of bytes. This prefix enables you to determine if the node is the client or the database server. The connection request is always sent by the client, but received by the database server (or listener).

   Example: Detailed Data Packets Sent in a Connection

   Example 16-9 shows detailed information from the -od option. The output shows all of the details sent along with the connect data in negotiating a connection.

   Example 16-9 trcasst -od Output

   ************************************************************************* * Trace Assistant * ************************************************************************* ---> Send 241 bytes - Connect packet Current NS version number is: 311. Lowest NS version number can accommodate is: 300. Global options for the connection: can receive attention no attention processing Don't care Maximum SDU size:2048 Maximum TDU size:32767 NT protocol characteristics: Test for more data Test operation Full duplex I/O Urgent data support Generate SIGURG signal Generate SIGPIPE signal Generate SIGIO signal Handoff connection to another Line turnaround value :0 Connect data length :183 Connect data offset :58 Connect data maximum size :512 Native Services wanted NAU doing O3LOGON - DH key foldedin Native Services wanted NAU doing O3LOGON - DH key foldedin Cross facility item 1: 0 Cross facility item 2: 0 Connection id : Ox000059F70000004C (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=sales-server)(PORT=1521)) (CONNECT_DATA=(SERVICE_NAME=sales.us.acme.com)(SRVR=SHARED)(CID=(PROGRAM=) (HOST=sales-server)(USER=joe)))) <--- Received 76 bytes - Redirect packet Redirect data length: 66 (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521)) ---> Send 241 bytes - Connect packet Current NS version number is: 311. Lowest NS version number can accommodate is: 300. Global options for the connection: can receive attention no attention processing Don't care Maximum SDU size:2048 Maximum TDU size:32767 NT protocol characteristics: Test for more data Test operation Full duplex I/O Urgent data support Generate SIGURG signal Generate SIGPIPE signal Generate SIGIO signal Handoff connection to another Line turnaround value :0 Connect data length :183 Connect data offset :58 Connect data maximum size :512 Native Services wanted NAU doing O3LOGON - DH key foldedin Native Services wanted NAU doing O3LOGON - DH key foldedin Cross facility item 1: 0 Cross facility item 2: 0 Connection id : Ox000059F70000007A (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=sales-server)(PORT=1521)) (CONNECT_DATA=(SERVICE_NAME=sales.us.acme.com)(SRVR=SHARED)(CID=(PROGRAM=) (HOST=sales-server)(USER=joe)))) <--- Received 32 bytes - Accept packet Accepted NS version number is: 310. Global options for the connection: no attention processing Don't care Accepted maximum SDU size: 2048 Accepted maximum TDU size: 32767 Connect data length: 0 Native Services wanted NAU doing O3LOGON - DH key foldedin Native Services wanted NAU doing O3LOGON - DH key foldedin ---> Send 153 bytes - Data packet Native Services negotiation packet version#: 150999040 Service data packet #0 for Supervisor has 3 subpackets Subpacket #0: Version #150999040 Subpacket #1: 0000000000000000 Subpacket #2: DEADBEEF0003000000040004000100010002 Service data packet #1 for Authentication has 3 subpackets Subpacket #0: Version #150999040 Subpacket #1: UB2: 57569 Subpacket #2: FCFF Service data packet #2 for Encryption has 2 subpackets Subpacket #0: Version #150999040 Subpacket #1: 000000000000000000 Service data packet #3 for Data Integrity has 2 subpackets Subpacket #0: Version #150999040 Subpacket #1: 000000 <--- Received 127 bytes - Data packet Native Services negotiation packet version#: 135290880 Service data packet #0 for Supervisor has 3 subpackets Subpacket #0: Version #135290880 Subpacket #1: 0000 Subpacket #2: DEADBEEF00030000000200040001 Service data packet #1 for Authentication has 2 subpackets Subpacket #0: Version #135290880 Subpacket #1: FBFF Service data packet #2 for Encryption has 2 subpackets Subpacket #0: Version #135290880 Subpacket #1: UB1: 0 Service data packet #3 for Data Integrity has 2 subpackets Subpacket #0: Version #135290880 Subpacket #1: UB1: 0 .... ---> Send 11 bytes - Marker packet One data byte. Hex character sent over to the server: 2 <--- Received 11 bytes - Marker packet One data byte. Hex character sent over to the server: 2 <--- Received 155 bytes - Data packet ---> Send 25 bytes - Data packet <--- Received 11 bytes - Data packet ---> Send 13 bytes - Data packet <--- Received 11 bytes - Data packet ---> Send 10 bytes - Data packet Data Packet flags: End of file ************************************************************************* * Trace Assistant has completed * *************************************************************************

   Two-Task Common Packet Examples

   TTC handles requests such as open cursor, select rows, and update rows that are directed to the database server. All requests are answered by the database server. If you request to logon, a response is returned from the database server that the request was completed.

   Example: Two-Task Common Summary Information with Summary TTC Information

   Summary information for TTC from the -ou option is different from other displays in that it shows two packets on each line, rather than one. This is done to mirror the request/response pairings process by which TTC operates.

   Example 16-10 shows all of the details sent along with the connect data in negotiating a connection.

   Example 16-10 trcasst -ou Output

   ************************************************************************* * Trace Assistant * ************************************************************************* Bytes Bytes Sent Rcvd Send operation(TTIPRO) 32 140 Send operation(TTIDTY) 33 22 Get the session key (OSESSKEY) 229 145 Generic authentication call (OAUTH) 368 1001 Send operation(TTIPFN) 44 144 Send operation(TTIPFN) 36 16 Parse a statement (OSQL) # 1 SELECT USER FROM ... 47 100 Fast upi calls to opial7 (OALL7) # 1 130 111 Fetch row (OFETCH) # 1 21 137 Close cursor (OCLOSE) # 1 17 11 New v8 bundled call (OALL8) # 0 !Keep Parse BEGI... 156 145 Send operation(TTIPFN) 51 16 Parse a statement (OSQL) # 1 SELECT ATTRIBUTE,... 186 100 Fast upi calls to opial7 (OALL7) # 1 246 111 Fetch row (OFETCH) # 1 21 126 Close cursor (OCLOSE) # 1 17 11 Send operation(TTIPFN) 36 16 Parse a statement (OSQL) # 1 SELECT CHAR_VALUE... 208 100 Fast upi calls to opial7 (OALL7) # 1 130 111 Fetch row (OFETCH) # 1 21 126 Close cursor (OCLOSE) # 1 17 11 Send operation(TTIPFN) 36 16 Fast upi calls to opial7 (OALL7) # 1 !Keep Parse BEGI... 183 41 Send operation(TTIRXD) 20 111 Close cursor (OCLOSE) # 1 17 11 New v8 bundled call (OALL8) # 0 Parse Fetch SELE... 165 278 Send operation(TTIPFN) 51 16 Parse a statement (OSQL) # 1 commit 31 100 Execute statement (OEXEC) # 1 number of rows: 1 25 100 Close cursor (OCLOSE) # 1 17 11 Send operation(TTIPFN) 36 16 Fast upi calls to opial7 (OALL7) # 1 !Keep Parse BEGI... 183 41 Send operation(TTIRXD) 60 111 Close cursor (OCLOSE) # 1 17 11 Send operation(TTIPFN) 36 16 Fast upi calls to opial7 (OALL7) # 1 !Keep Parse BEGI... 183 41 Send operation(TTIRXD) 20 111 Close cursor (OCLOSE) # 1 17 11 New v8 bundled call (OALL8) # 0 Parse Fetch sele... 144 383 New v8 bundled call (OALL8) # 1 !Keep Fetch 121 315 Logoff off of Oracle (OLOGOFF) 13 11 ************************************************************************* * Trace Assistant has completed * *************************************************************************

   Output is displayed in the following format:

   description TTC_message cursor_number SQL_statement bytes_sent bytes_received

   On each line of the output, the first item displayed is the actual request made. The second item shows on what cursor that operation has performed. The third item is either a listing of the SQL command or flag that is being answered. The number of bytes sent and received are displayed at the far right. A flag can be one of the following:

   !PL/SQL = Not a PL/SQL request COM = Commit IOV = Get I/O Vector DEFN = Define EXEC = Execute FETCH = Fetch CAN = Cancel DESCSEL = Describe select DESCBND = Describe Bind BND = Bind PARSE = Parse EXACT = Exact

   Example: Detailed SQL Information on Top of Summary Two-Task

   Example 16-11 shows detailed SQL information from the -ouq option.

   Example 16-11 trcasst -ouq Output

   ************************************************************************* * Trace Assistant * ************************************************************************* Bytes Bytes Sent Rcvd Send operation(TTIPRO) 32 140 Send operation(TTIDTY) 33 22 Get the session key (OSESSKEY) 229 145 Generic authentication call (OAUTH) 368 1001 Send operation(TTIPFN) 44 144 Send operation(TTIPFN) 36 16 Parse a statement (OSQL) # 1 47 100 SELECT USER FROM DUAL Fast upi calls to opial7 (OALL7) # 1 130 111 Fetch row (OFETCH) # 1 21 137 Close cursor (OCLOSE) # 1 17 11 New v8 bundled call (OALL8) # 0 !Keep Parse 156 145 BEGIN DBMS_OUTPUT.DISABLE; END; Send operation(TTIPFN) 51 16 Parse a statement (OSQL) # 1 186 100 SELECT ATTRIBUTE,SCOPE,NUMERIC_VALUE,CHAR_VALUE,DA TE_VALUE FROM SYSTEM.PRODUCT_PRIVS WHERE (UPPER('S QL*Plus') LIKE UPPER(PRODUCT)) AND (UPPER(USER) LI KE USERID) Fast upi calls to opial7 (OALL7) # 1 246 111 Fetch row (OFETCH) # 1 21 126 Close cursor (OCLOSE) # 1 17 11 Send operation(TTIPFN) 36 16 Parse a statement (OSQL) # 1 208 100 SELECT CHAR_VALUE FROM SYSTEM.PRODUCT_PRIVS WHERE (UPPER('SQL*Plus') LIKE UPPER(PRODUCT)) AND ((UPPE R(USER) LIKE USERID) OR (USERID = 'PUBLIC')) AND ( UPPER(ATTRIBUTE) = 'ROLES') Fast upi calls to opial7 (OALL7) # 1 130 111 Fetch row (OFETCH) # 1 21 126 Close cursor (OCLOSE) # 1 17 11 Send operation(TTIPFN) 36 16 Fast upi calls to opial7 (OALL7) # 1 !Keep Parse 183 41 BEGIN DBMS_APPLICATION_INFO.SET_MODULE(:1,NULL); E ND; Send operation(TTIRXD) 20 111 Close cursor (OCLOSE) # 1 17 11 New v8 bundled call (OALL8) # 0 Parse Fetch 165 278 SELECT DECODE('A','A','1','2') FROM DUAL Send operation(TTIPFN) 51 16 Parse a statement (OSQL) # 1 31 100 commit Execute statement (OEXEC) # 1 number of rows: 1 25 100 Close cursor (OCLOSE) # 1 17 11 Send operation(TTIPFN) 36 16 Fast upi calls to opial7 (OALL7) # 1 !Keep Parse 183 41 BEGIN DBMS_APPLICATION_INFO.SET_MODULE(:1,NULL); E ND; Send operation(TTIRXD) 60 111 Close cursor (OCLOSE) # 1 17 11 Send operation(TTIPFN) 36 16 Fast upi calls to opial7 (OALL7) # 1 !Keep Parse 183 41 BEGIN DBMS_APPLICATION_INFO.SET_MODULE(:1,NULL); E ND; Send operation(TTIRXD) 20 111 Close cursor (OCLOSE) # 1 17 11 New v8 bundled call (OALL8) # 0 Parse Fetch 144 383 select * from dept New v8 bundled call (OALL8) # 1 !Keep Fetch 121 315 Logoff off of Oracle (OLOGOFF) 13 11 ************************************************************************* * Trace Assistant has completed * *************************************************************************

   Example: Two-Task Common Summary Information with Detailed TTC Information

   Example 16-12 shows detailed TTC information from the -ot option.

   Example 16-12 trcasst -ot Output

   ************************************************************************* * Trace Assistant * ************************************************************************* Set protocol (TTIPRO) Operation 01 (con) Send protocol version=6 Originating platform: SVR4-be-8.1.0 Set protocol (TTIPRO) Operation 01 (con) Receive protocol version=6 Destination platform: SVR4-be-8.1.0 Set datatypes (TTIDTY) Set datatypes (TTIDTY) Start of user function (TTIFUN) (OSESSKEY) Return opi parameter (TTIRPA) Start of user function (TTIFUN) (OAUTH) Return opi parameter (TTIRPA) Start of user function (TTIFUN) session operations 71 (O71SESOPN) (switch session) Return opi parameter (TTIRPA) Start of user function (TTIFUN) Get Oracle version/date string in new format (OVERSION) Return opi parameter (TTIRPA) Oracle Enterprise Edition Release 10.1.0.2.0 With the Partitioning option JServer Release 10.1.0.2.0 Start of user function (TTIFUN) session operations 71 (O71SESOPN) (switch session) Return opi parameter (TTIRPA) Start of user function (TTIFUN) Open a cursor (OOPEN) Return opi parameter (TTIRPA) Cursor #: 1 Start of user function (TTIFUN) Parse a statement (OSQL) Cursor # 1 SELECT USER FROM DUAL ************************************************************************* * Trace Assistant has completed * *************************************************************************

   Connection Example

   Example 16-13 shows output from the -la option. The output shows the following information:

   • Connect IDs received

   • Socket ID on which this connection has come

   • Operation

     Receive identifies the trace as a database server trace; Send identifies the trace as a client trace. In this output, Receive is the operation.

   • MULTIPLEX attribute of the DISPATCHERS parameter is set to ON

   • 32-bit session ID

   • Connect data information received

   Example 16-13 trcasst -la Output

   ************************************************************************* * Trace Assistant * ************************************************************************* Connection ID: 00000B270000000B Socket Id: 15 Operation: Receive Multiplex: ON Session Id: 8362785DE4FC0B19E034080020F793E1 Connect Data: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=sales-server)(PORT=1521)) (CONNECT_DATA=(SERVER=shared) (SERVICE_NAME=sales.us.acme.com)(CID=(PROGRAM=)(HOST=sales-server) (USER=oracle)))) Connection ID: 00000B240000000B Socket Id: 15 Operation: Receive Multiplex: ON Session Id: 8362785DE4FB0B19E034080020F793E1 Connect Data: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=sales-server)(PORT=1521)) (CONNECT_DATA=(SERVER=shared) (SERVICE_NAME=sales.us.acme.com)(CID=(PROGRAM=)(HOST=sales-server) (USER=oracle)))) Connection ID: 00000B1F00000008 Socket Id: 15 Operation: Receive Multiplex: ON Session Id: 8362785DE4F90B19E034080020F793E1 Connect Data: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=sales-server)(PORT=1521)) (CONNECT_DATA=(SERVER=shared) (SERVICE_NAME=sales.us.acme.com)(CID=(PROGRAM=)(HOST=sales-server) (USER=oracle)))) ************************************************************************* * Trace Assistant has completed * *************************************************************************

   Example 16-14 shows output for connection ID 00000B1F00000008 from the -li 00000B1F00000008 option.

   Example 16-14 trcasst -li Output

   ************************************************************************* * Trace Assistant * ************************************************************************* <--- Received 246 bytes - Connect packet Current NS version number is: 310. Lowest NS version number can accommodate is: 300. Global options for the connection: Can receive attention No attention processing Don't care Maximum SDU size: 2048 Maximum TDU size: 32767 NT protocol characteristics: Test for more data Test operation Full duplex I/O Urgent data support Generate SIGURG signal Generate SIGPIPE signal Generate SIGIO signal Handoff connection to another Line turnaround value: 0 Connect data length: 188 Connect data offset: 58 Connect data maximum size: 512 Native Services wanted NAU doing O3LOGON - DH key foldedin Native Services wanted NAU doing O3LOGON - DH key foldedin Cross facility item 1: 0 Cross facility item 2: 0 Connection id: Ox00000B1F00000008 (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=sales-server)(PORT=1521)) (CONNECT_DATA=(SERVER=shared)(SERVICE_NAME=sales.us.acme.com) (CID=(PROGRAM=)(HOST=sales-server)(USER=oracle)))) ---> Send 114 bytes - Accept packet Accepted NS version number is: 310. Global options for the connection: No attention processing Don't care Accepted maximum SDU size: 2048 Accepted maximum TDU size: 32767 Connect data length: 0 Native Services wanted NAU doing O3LOGON - DH key foldedin Native Services wanted NAU doing O3LOGON - DH key foldedin Connection Time out: 1000 Tick Size: 100 Reconnect Data: (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=34454)) Session Id: 8362785DE4F90B19E034080020F793E1 <--- Received 164 bytes - Data packet Native Services negotiation packet version#: 135290880 Service data packet #0 for Supervisor has 3 subpackets Subpacket #0: Version #135290880 Subpacket #1: 0000000000000000 Subpacket #2: DEADBEEF0003000000040004000100010002 Service data packet #1 for Authentication has 3 subpackets Subpacket #0: Version #135290880 Subpacket #1: UB2: 57569 Subpacket #2: FCFF Service data packet #2 for Encryption has 2 subpackets Subpacket #0: Version #135290880 Subpacket #1: 0000000000 Service data packet #3 for Data Integrity has 2 subpackets Subpacket #0: Version #135290880 Subpacket #1: 0000 ---> Send 143 bytes - Data packet Native Services negotiation packet version#: 135290880 Service data packet #0 for Supervisor has 3 subpackets Subpacket #0: Version #135290880 Subpacket #1: 0000 Subpacket #2: DEADBEEF00030000000200040001 Service data packet #1 for Authentication has 2 subpackets Subpacket #0: Version #135290880 Subpacket #1: FBFF Service data packet #2 for Encryption has 2 subpackets Subpacket #0: Version #135290880 Subpacket #1: UB1: 0 Service data packet #3 for Data Integrity has 2 subpackets Subpacket #0: Version #135290880 Subpacket #1: UB1: 0 <--- Received 48 bytes - Data packet Set protocol (TTIPRO) Operation 01 (con) Receive protocol version=6 Destination platform: SVR4-be-8.1.0 ---> Send 156 bytes - Data packet Set protocol (TTIPRO) Operation 01 (con) Send protocol version=6 Originating platform: SVR4-be-8.1.0 <--- Received 49 bytes - Data packet Set datatypes (TTIDTY) ---> Send 38 bytes - Data packet Set datatypes (TTIDTY) <--- Received 245 bytes - Data packet Start of user function (TTIFUN) Get the session key (OSESSKEY) ---> Send 161 bytes - Data packet Return opi parameter (TTIRPA) ... ************************************************************************* * Trace Assistant has completed * *************************************************************************

   Statistics Example

   The type of statistics gathered is approximately on how many TTC calls, packets and bytes were sent and received between the network partners. Example 16-14 shows typical trace file statistics from the -s option.

   Example 16-15 trcasst -s Output

   ************************************************************************* * Trace Assistant * ************************************************************************* ---------------------- Trace File Statistics: ---------------------- Total number of Sessions: 3 DATABASE: Operation Count: 0 OPENS, 21 PARSES, 21 EXECUTES, 9 FETCHES Parse Counts: 9 PL/SQL, 9 SELECT, 0 INSERT, 0 UPDATE, 0 DELETE, 0 LOCK, 3 TRANSACT, 0 DEFINE, 0 SECURE, 0 OTHER Execute counts with SQL data: 9 PL/SQL, 0 SELECT, 0 INSERT, 0 UPDATE, 0 DELETE, 0 LOCK, 0 TRANSACT, 0 DEFINE, 0 SECURE, 0 OTHER Packet Ratio: 6.142857142857143 packets sent per operation Currently opened Cursors: 0 Maximum opened Cursors : 0 ORACLE NET SERVICES: Total Calls : 129 sent, 132 received, 83 oci Total Bytes : 15796 sent, 13551 received Average Bytes: 122 sent per packet, 102 received per packet Maximum Bytes: 1018 sent, 384 received Grand Total Packets: 129 sent, 132 received ************************************************************************* * Trace Assistant has completed * *************************************************************************

   Contacting Oracle Support Services

   If you are still unable to resolve your problems, or if you are requested to contact Oracle Support Services to report the error, please have the following information at hand:

   • The hardware and operating system release number on which the application is running

   • The up-to-five-digit release number of all the Oracle networking products involved in the current problem

   • The third-party vendor and version you are using

   • If you encountered one or more error codes or messages, the exact code numbers and message texts in the order they appeared

   • The kind of links that exist between the client and server

   • A description of what does work

   • The exact error message, if there is one

   • An Net8 Services trace, if possible; if not, the log file is sufficient