Troubleshooting Oracle Net Services

Oracle Net Services provides methods for understanding, testing and resolving network problems. Oracle Database includes utilities, and log and trace files for testing and diagnosing network connection and problems.

The TNSPING and TRCROUTE utilities test connectivity. The log and trace files keep track of the interaction between network components as errors occur. Evaluating this information helps to diagnose and troubleshoot network problems.

Understand the common testing procedures and network errors, and outline procedures for resolving problems. Also, learn methods for logging and tracing error information to diagnose and troubleshoot more complex network problems.

Understanding Automatic Diagnostic Repository

The Automatic Diagnostic Repository (ADR) (ADR) is a system-wide tracing and logging central repository.

The repository is a file-based hierarchical data store for depositing diagnostic information, including network tracing and logging information.

The ADR home is the unit of the ADR directory that is assigned to an instance of an Oracle product. Each database instance has its own ADR home. Similarly, each listener, Oracle Connection Manager, and client instance has its own ADR home.

In case of a process failure, an incident is generated. The incident dump files are located in the ADR_BASE/ADR_HOME/incident/ directory, By default, ADR_BASE is ORACLE_BASE if the ORACLE_BASE variable is set. If the variable is not set, then ADR_BASE is ORACLE_HOME/log. ADR_BASE can be set to any location.

The incident dump file location can be found inside the process trace file.

The location of an ADR home is given by the following path, which starts at the ADR base directory:

diag/product_type/product_id/instance_id

The following table lists the values of the path components for an Oracle Net Listener instance.

Table 1 ADR Home Path Components for an Oracle Net Listener Instance

Path Component Value for Oracle Net Listener
product_type tnslsnr
product_id host name
instance_id listener alias name

The following figure illustrates the directory hierarchy of the ADR for an Oracle Net Listener instance. Other ADR homes for other Oracle products or components, such as Automatic Storage Management (ASM) or Oracle Database, can exist within this hierarchy, under the same ADR base.

Figure 1: Directory Structure for an Oracle Net Listener Instance

Description of the illustration netag136.gif

The following table lists the values of the path components for an Oracle Connection Manager instance.

Table 2 ADR Home Path Components for an Oracle Connection Manager Instance

Path Component Value for Oracle Connection Manager
product_type netcman
product_id host name
instance_id Oracle Connection Manager instance name

The following figure illustrates the directory hierarchy of the ADR for an Oracle Connection Manager instance. Other ADR homes for other Oracle products or components, such as Oracle ASM or Oracle Database, can exist within this hierarchy, under the same ADR base.

Figure 2: Directory Structure for an Oracle Connection Manager Instance

Description of the illustration netag137.gif

Within the ADR home directory are subdirectories where each instance, such as the database, listener, Oracle Connection Manager, or client, stores diagnostic data. The following table lists all the subdirectories shown in the preceding figure and their contents.

Table 3 ADR Home Subdirectories

Subdirectory Name Contents
alert The XML-formatted log named log.xml.
cdump Core files.
incident Multiple subdirectories, in which each subdirectory is named for a particular incident, and each contains dumps pertaining only to that incident.
trace Background and server process trace files, SQL trace files, and text version of the log.xml file in the alert directory.
(others) Other subdirectories of ADR home, which store incident packages, health monitor reports, and other information.

The ADR_BASE directory is the physical location in which one or more ADR homes are placed. Conceptually, it is the root directory of ADR.

Non-ADR (meaning that the DIAG_ADR_ENABLED parameter is set to OFF) diagnostic and tracing methods are still current and applicable but the parameters are ignored if ADR is enabled. ADR is enabled by default.

Diagnostic parameters are found in the following configuration files:

The following table compares usage of diagnostic parameters found in the sqlnet.ora file, which is used in both ADR-based and non-ADR-based diagnostics.

Table 4 sqlnet.ora File Diagnostic Parameter Comparison

Parameter DIAG_ADR_ENABLED=ON DIAG_ADR_ENABLED=OFF
ADR_BASE Enabled Disabled
TRACE_LEVEL_CLIENT Enabled Enabled
TRACE_LEVEL_SERVER Enabled Enabled
TRACE_DIRECTORY_CLIENT Disabled Enabled
TRACE_FILE_CLIENT Disabled Enabled
TRACE_UNIQUE_CLIENT Disabled Enabled
LOG_DIRECTORY_CLIENT Disabled Enabled
LOG_FILE_CLIENT Disabled Enabled
LOG_DIRECTORY_SERVER Disabled Enabled
TRACE_DIRECTORY_SERVER Disabled Enabled
TRACE_FILE_SERVER Disabled Enabled

The following table compares usage of diagnostic parameters found in the listener.ora file, which is used in both ADR-based and non-ADR-based diagnostics.

Table 5 listener.ora File Diagnostic Parameter Comparison

Parameter DIAG_ADR_ENABLED=ON DIAG_ADR_ENABLED=OFF
ADR_BASE_listener_name Enabled Disabled
LOGGING_listener_name Enabled Enabled
TRACE_LEVEL_listener_name Enabled Enabled
TRACE_TIMESTAMP_listener_name Enabled Enabled
LOG_DIRECTORY_CLIENT_listener_name Disabled Enabled
LOG_FILE_CLIENT_listener_name Disabled Enabled
TRACE_DIRECTORY_CLIENT_listener_name Disabled Enabled
TRACE_FILELEN_listener_name Disabled Enabled
TRACE_FILENO_listener_name Disabled Enabled

The following table compares usage of diagnostic parameters found in the cman.ora file, which is used in both ADR-based and non-ADR-based diagnostics.

Table 6 cman.ora File Diagnostic Parameter Comparison

Parameter DIAG_ADR_ENABLED=ON DIAG_ADR_ENABLED=OFF
ADR_BASE Enabled Disabled
LOG_LEVEL Enabled Enabled
TRACE_LEVEL Enabled Enabled
TRACE_TIMESTAMP Enabled Enabled
LOG_DIRECTORY Disabled Enabled
TRACE_DIRECTORY Disabled Enabled
TRACE_FILELEN Disabled Enabled
TRACE_FILENO Disabled Enabled

ADRCI: ADR Command Interpreter

ADRCI is a command-line tool that is part of the fault diagnosability infrastructure. ADRCI enables you to do the following:

Diagnostic data includes incident and problem descriptions, trace files, dumps, health monitor reports, alert log entries, and so on.

ADRCI has a rich command set, and can be used in interactive mode or within scripts. In addition, ADRCI can run scripts of ADRCI commands in the same way that SQL*Plus runs scripts with SQL and PL/SQL commands.

To view trace files using ADRCI, enter ADRCI at a command line. The following are common ADRCI commands used to check a client:

Client Side

adrci> SHOW ALERT
adrci> SHOW BASE -product client
adrci> SET BASE -product client
adrci> SHOW TRACEFILE
adrci> SHOW TRACE trace_file.trc
adrci> SHOW SPOOL

In the preceding commands, the SHOW ALERT command shows the log.xml file in a text editor, such as VI. The SHOW BASE -product client command displays the value of the ADR_BASE directory for the client. Use that value for client in the SET BASE command.

The following are common ADRCI commands used to check a server:

Server Side

adrci> SHOW BASE
adrci> SHOW TRACEFILE
adrci> SHOW TRACE trace_file.trc

Other ADRCI command options are available for a more targeted Oracle Net trace file analysis. Type HELP at the ADRCI prompt for help documentation.

See Also: Oracle Database Utilities for additional information about ADRCI

Diagnosing Oracle Net Services

Any underlying fault, noticeable or not, is reported by Oracle Net Services with an error number or message. The error number and message provide useful information for diagnosing the problem, but may not always identify the actual problem.

This section helps you determine the parts of Oracle Net Services that function properly. You can also determine one of the following categories to which the fault belongs:

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

Diagnosing Server Problems

To start diagnosing server problems, you should answer the following questions:

If you answered yes to either of the preceding questions, then go to “Diagnosing Client Problems”.

If you are unsure, or answered no to any of the preceding questions, then use the tasks in this section to diagnose the problem. Diagnosing Oracle Net Services on the server involves the following tasks:

Task 1 Verify the Database is Running

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

SQLPLUS system
Enter password: password

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

Task 2 Perform a Loopback Test

A loopback test uses Oracle Net to go from the database server back to itself, bypassing the Interprocess Communication (IPC) protocol. Many network protocols provide a means of testing network connections. The PING utility can be used with a TCP/IP network. Performing a successful loopback verifies that Oracle Net is functioning on the database server.

The following procedure describes how 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 “Using Localized Management”.

  2. Start Oracle Net Manager.

    See Also: “Using Oracle Net Manager to Configure Oracle Net Services”

  3. In the navigator, expand the Directory or Local option.

  4. Expand Service Naming to view the available network service and database names.

  5. Select the network service name or database service.

  6. Choose Command, and then select Test Net Service.

    Testing assumes the listener and database are running. If they are not, then see “Starting Oracle Net Listener and the Oracle Database Server” to start components.

    During testing, a Connection Test dialog box appears, providing status and test results. A successful test results in the following message:

    The connection test was successful.

    If the test was successful, then proceed to step 7.

    If the test was not successful, then do the following:

    1. Ensure the database and listener are running, and then click Test.

    2. Click Change Login to change the username and password for the connection, and then click Test.

    • If the loopback test passes, then go to “Diagnosing Client Problems”.

    • If the loopback test continues to fail, then contact Oracle Support Services.

  7. Click **Close** to close the Connect Test dialog box.

Diagnosing Client Problems

Verify at least one of the following statements. This will help you decide if it is a client problem.

The following procedure describes how to perform diagnostics on the client:

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

    On Linux and UNIX platforms you can use the ADAPTERS utility to verify protocol support. On the database server, run the following command from the ORACLE_HOME/bin directory to display the protocol support, naming methods, and security options linked with the oracle executable:

    adapters ./oracle

    The adapters utility displays output similar to the following:

    Installed Oracle Net transport protocols are:

    IPC
    BEQ
    TCP/IP
    SSL
    RAW
    SDP/IB

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 crypto-checksumming (for FIPS)
    SHA-1 crypto-checksumming
    Kerberos v5 authentication
    RADIUS authentication

    On the client, run the adapters command from the ORACLE_HOME/bin directory 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
    SDP/IB
    Exadirect

Installed Oracle Net naming methods are:

    Local Naming (tnsnames.ora)
    Oracle Directory Naming
    Oracle Host 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

    Note:

    • The DES, DES40, 3DES 112, 3DES 168, RC4 40, RC4 56, RC4 128, RC4 256, and MD5 algorithms are deprecated in this release.

      To transition your Oracle Database environment to use stronger algorithms, download and install the patch described in My Oracle Support note 2118136.2.

    • RAW is an internal protocol used by Oracle Net.

    See Also: Oracle Database Administrator’s Reference for additional information about the adapters utility

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

    Table 7 Verify Base Connectivity for Network

    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.

  3. Ensure that the Oracle Net foundation layer and the appropriate Oracle protocol support are present by verifying that all Oracle Net Services software has been installed for the client.

  4. Ensure that the client computer has the tnsnames.ora and the sqlnet.ora files in the correct locations.

    See Also: “Using Localized Management”

    If any other working client computers are connecting to the selected Oracle Database, then back up your existing files and copy both the working tnsnames.ora and sqlnet.ora files from the working client computer to the non-working clients. This eliminates the possibility of errors in the files.

  5. Test the Oracle Net foundation layer. You can test using the following command to connect to SQL*Plus:

    SQLPLUS user/password@connect_string

    Note: Do not use the TNSPING utility. The TNSPING utility works like the TCP/IP ping utility and does not create and open a socket, nor does it connect with the listener. It only shows that the listener is present on the database server.

  6. If the connection still fails, then do the following:

    1. Use tracing, as described in section “Tracing Error Information for Oracle Net Services”.

    2. Check the Oracle Support Services website for a specific diagnostics bulletin on the error received.

    3. Contact Oracle Support Services.

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, then applications such as SQL*Plus, that depend on network services from Oracle Net Services, normally generate an error message.

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

oerr code error_number

In the preceding command, code is the type of message, such as ORA and TNS, and error_number is the number associated with the error message.

The following is a list of the most common network error messages:

See Also: Oracle Database Error Messages for a complete listing of error messages

ORA-03113: End-of-file on Communication Channel

This message indicates that an error has occurred on the database server.

Check the alert_sid.log file on the server. 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, or it may indicate that the server has gone down.You may need to modify your retransmission count.

ORA-12154: Could Not Resolve the Connect Identifier Specified

This message indicates that a connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a network service name then the network service name could not be found in a naming method repository, or the repository could not be located or reached.

Perform the following steps:

  1. Check the type of naming adapters listed in the NAMES.DIRECTORY_PATH parameter in the sqlnet.ora file. If none are configured, then use the adapters command to determine which adapters are in use. The following example shows the adapters:

    $ adapters
             ...
     Installed Oracle Net naming methods are:

         Local Naming (tnsnames.ora)
         Oracle Directory Naming
         Oracle Host Naming
         NIS Naming

    The network service name given in the connect string should be defined for at least one of the naming methods.

  2. Check the resolution path for each adapter for possible problems. For example, ensure that the name given in the connect string is correct and complete, using the full name of the network service if necessary.

In addition to the preceding steps, perform the steps depending on your naming methods:

ORA-12154 Error When Using the Local Naming Method

Perform the following steps when using the local naming method:

  1. Verify that the tnsnames.ora file exists and is in the correct location. The location is either the ORACLE_HOME/network/admin directory or the directory specified by the TNS_ADMIN environment variable.

  2. Verify there is an entry in the tnsnames.ora file for the name given in the connect string. This network service name should match the name in the tnsnames.ora file exactly if the name is simple and there is not NAMES_DEFAULT_DOMAIN in the sqlnet.ora file, or the network service name is a fully-qualified name. If the network service name in the connect string is simple, then check the NAMES_DEFAULT_DOMAIN parameter in the sqlnet.ora file. Its value is appended to the network service name given in the connect string. This fully-qualified name should be the entry in the tnsnames.ora file.

  3. If you are connecting from a login dialog box, then verify that you are not placing an at sign (@) before the connect network service name.

  4. Activate client tracing, and repeat the operation.

ORA-12154 Error When Using the Directory Naming Method

Perform the following steps when using the directory naming method:

  1. Verify the ldap.ora file exists and is in the correct location. The following directories are searched for ldap.ora file in the order given. The ldap.ora file found will be used.

    • The directory specified by the TNS_ADMIN environment variable.

    • The ORACLE_HOME/network/admin directory.

    • The directory specified by the LDAP_ADMIN environment variable.

    • The ORACLE_HOME/ldap/admin directory.

  2. Verify that the parameters defined in the ldap.ora file are correct, as follows:

    • The DIRECTORY_SERVERS parameter defines the correct host and port for one or more valid LDAP servers.

    • The DEFAULT_ADMIN_CONTEXT parameter defines the location of the Oracle Context in this directory which should include the network service entry.

    If the ldap.ora file does not exist, then these parameters are resolved using automatic discovery.

  3. Verify that the LDAP server host and port are defined in DNS.

  4. Verify that the directory has the default Oracle Context defined.

  5. Use the ldapsearch utility or a directory administration tool to verify that the network service object exists in the Oracle Context at the location given by the value of the DEFAULT_ADMIN_CONTEXT parameter.

ORA-12154 Error When Using the Easy Connect Naming Method

Verify that the host name give is correct, and is defined in the local host name resolution service, such as local hosts file, DNS, and so on.

ORA-12154 Error When Using the External Naming Method

Perform the following steps when using the external naming method:

  1. Verify that the NIS file for tnsnames map is properly set up.

  2. Check that the network service name matches the tnsnames entry as described in “ORA-12154 Error When Using the Local Naming Method”.

See Also:

ORA-12170: Connect Timeout Occurred

This message indicates that 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:

TNS-12500 or ORA-12500: Listener Failed to Start a Dedicated Server Process

These messages indicate that the listener failed to start the Oracle program. Possible reasons include:

In some cases, these errors can be caused by the same conditions which cause the following errors:

Perform the appropriate action:

ORA-12514: Listener Does Not Currently Know of Service Requested in Connect Descriptor

This message indicates that 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.

Perform the following steps:

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

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

  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:

ORA-12520: Listener Could Not Find Available Handler for Requested Type of Server

This message indicates that the type of service handler requested by the client is incorrect or not registered for the requested SERVICE_NAME/INSTANCE_NAME parameters, or the database instance is not registered with the listener.

If you suspect the problem is the wrong type of service handler, then perform the following steps:

  1. If (server=value) is set in the connect descriptor, then 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.

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

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

See Also: “Monitoring Services of a Listener” for additional information about service handlers

ORA-12521: Listener Does Not Currently Know of Instance Requested in Connect Descriptor

This message indicates that the instance name in the connect descriptor is incorrect, or the database instance is not registered with the listener.

Perform the following steps:

  1. Ensure the service name specified in the connect descriptor is correct.

  2. Ensure the database instance is running. If the instance not running, then 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” for additional information about SERVICES command

ORA-12525: Listener Has Not Received Client’s Request in Time Allowed

This message indicates that 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:

ORA-12533: Illegal Address Parameters

This message indicates that the protocol specific parameters in the ADDRESS section of the designated connect descriptor are incorrect.

Correct the protocol address.

Note: This error is often caused by hand-editing of the tnsnames.ora file. Only edit the tnsnames.ora file using Oracle Enterprise Manager Cloud Control or Oracle Net Manager.

See Also: Oracle Database Net Services Reference for correct protocol syntax

TNS-12540 or ORA-12540: TNS:Internal Limit Restriction Exceeded and TNS-00510: Internal Limit Restriction Exceeded

These messages indicate that an internal limit has been exceeded. Possible limits include the following:

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 or ORA-12500 error is also returned. In some cases, these errors can be caused by the same conditions which cause TNS-12549 or ORA-12549, and TNS-00519 errors.

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 or ORA-12541: TNS:No Listener

These messages indicate that the connection request could not be completed because the listener is not running.

Perform the following actions:

TNS-12549 or ORA-12549: TNS:Operating System Resource Quota Exceeded and TNS-00519: Operating System Resource Quota Exceeded

These messages indicate that a quota or hard limit imposed by the operating system has been exceeded.

Possible limits include:

Perform the appropriate action:

TNS-12560 or ORA-12560: TNS:Protocol Adapter Error Occurred

These messages indicate that 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 are caused by the same conditions which cause TNS-00510, TNS-00519, TNS-12540, ORA-12540, TNS-12549 or ORA-12549 errors.

These errors occur on Microsoft Windows systems only. Perform the following actions:

  1. Select Run from the Microsoft Windows Start menu.

  2. Enter MSCONFIG in the Open field.

  3. Go to the Services tab.

  4. Enable OracleServicesid if it is disabled.

  5. Restart the computer.

  6. Check that Oracle Services started.

Directory Naming Errors

Directory naming issues associated with connectivity errors for database service or network 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. The ldifwrite tool is an Oracle Internet Directory tool.

The ldifwrite tool can be used to convert all or part of the information residing in a directory server to 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-8 lists ldifwrite tool arguments and descriptions for each.

Table 8 ldifwrite Arguments

Argument Description
-cnet_service_name/database_service The network service name or database service name that connects to the directory server.
-bbase_DN The base of the subtree to be written out in LDIF format.
-fldif_file The output file name.

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

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

Note: Check the ldap.ora file to determine the base_DN value. It is the same as the DEFAULT_ADMIN_CONTEXT entry in the ldap.ora file.

Troubleshooting Suggestions for Oracle Net Services

These are the suggestions for diagnosing network problems and troubleshooting Oracle Connection Manager in Traffic Director Mode.

Questions to Consider When Troubleshooting Oracle Net Services

These questions help you in diagnosing network problems.

Example of Troubleshooting a TNS-12154 Error

This section offers some solutions for the TNS-12154 error. The TNS-12154 error is encountered when SQL*Net cannot find the connect identifier specified for a connection in the tnsnames.ora file or other naming adapter.

Before attempting to resolve the problem, it may be helpful to print out or view the tnsnames.ora file and the sqlnet.ora file. Looking at these files at the same time is helpful because references are made to both.

In this example, the tnsnames.ora and sqlnet.ora files are located in the default network administration directory on the client system.

Be sure that the tnsnames.ora file and the sqlnet.ora file resemble the following examples.

The following is an example of a tnsnames.ora file:

Example 16-1 tnsnames.ora Sample

DEV1.WORLD =
     (DESCRIPTION =
           (ADDRESS =
             (PROTOCOL = TCP)
             (HOST = 192.0.2.56)
             (PORT = 1521)
           )
       (CONNECT_DATA =
         (SERVICE_NAME = sales.example.com)
       )
     )

The following is an example of a sqlnet.ora file:

Example 16-2 sqlnet.ora Sample

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

The alias in Example 16-1 is DEV1.WORLD. However, the NAMES.DEFAULT_DOMAIN = WORLD parameter does not exist in Example 16-2. To fix this problem, add the NAMES.DEFAULT_DOMAIN = WORLD parameter anywhere in the sqlnet.ora file. Save the file, and try the connection again.

Logging Error Information for Oracle Net Services

All errors encountered by 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 about on-screen error messages. The error stack in the log file shows the state of the software at various layers.

To ensure that all errors are recorded, logging cannot be disabled on clients or name servers. Furthermore, only an administrator may replace or erase log files. The log file for the listener includes audit trail information about every client connection request, and most listener control commands.

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.

Table 9 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.
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 are involved in the connection (open, close functions).

  • 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). These layers map Oracle Net foundation layer functionality to industry-standard protocols.

Understanding Error Stack Messages

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.

Suppose that a user of a client application tries to establish a connection with a database server using Oracle Net and TCP/IP, by entering the following commands:

SQLPLUS scott@example.com
Enter password: password

When the commands are entered, 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.

On the client side, the sqlnet.log file (as shown in the following example) 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=scott)))(ADDRESS_LIST=(ADDRESS=
   (PROTOCOL=ipc)(KEY=trace))(ADDRESS=(PROTOCOL=tcp)
   (HOST=lala)(PORT=1521))))

VERSION INFORMATION:
TNS for Linux:
Oracle Bequeath NT Protocol Adapter for Linux:
Unix Domain Socket IPC NT Protocol Adaptor for Linux:
TCP/IP NT Protocol Adapter for Linux:
  Tracing to file: /home/db_tracefiles/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. When using ADR, the default, the log file names are log.xml in the appropriate alert directory.

The following table lists the default log file names and the components that generate the log files that appear in the ADR/diag/instance_name/trace directory.

Table 10 Log File Names When Using ADR

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

Oracle Network Log File Segmentation

The maximum size and number of text log files can be configured for Oracle Network components such as Oracle Net Listener, Oracle Connection Manager, and Global Service Manager.

This feature allows better management of log files, particularly in Cloud environments. This is an ADR only feature and applicable to both text and XML log files.

About the Logging Parameters

Parameters that control logging, including the type and amount of information logged, and the location where the files are stored, are set in the configuration file of each network component.

Table 11 Location of Log Parameters

Network Component Configuration File
Oracle Connection Manager processes cman.ora
Listener listener.ora
Client sqlnet.ora
Database server sqlnet.ora

Note: If the ADR_ENABLED parameter is set to ON, then all logging parameters are set by ADR. Using Oracle Net Manager to change the parameters will not work.

Related Topics

sqlnet.ora Log Parameters

You can set these log parameters in the sqlnet.ora file.

Table 12 sqlnet.ora Log Parameters

sqlnet.ora Parameter Oracle Net Manager Field Description
ADR_BASE You must set this parameter manually.

The ADR_BASE parameter specifies the base directory for storing tracing and logging incidents.

Use this parameter when DIAG_ADR_ENABLED is set to ON.

DIAG_ADR_ENABLED You must set this parameter manually.

The DIAG_ADR_ENABLED parameter indicates whether ADR tracing is enabled.

When the DIAG_ADR_ENABLED parameter is set to OFF, non-ADR file tracing is used.

LOG_DIRECTORY_CLIENT Client Information: Log Directory The destination directory for the client log file. By default, the client directory is the current working directory. This parameter is disabled when ADR_ENABLED is set to ON.
LOG_DIRECTORY_SERVER Server Information: Log Directory The destination directory for the database server log files. By default the server directory is ORACLE_HOME/network/log. This parameter is disabled when ADR_ENABLED is set to ON.
LOG_FILE_CLIENT Client Information: Log File The name of the log file for the client. By default the log name is sqlnet.log.
LOG_FILE_SERVER You must set this parameter manually. The name of the log file for the database server. By default the log name is sqlnet.log.

listener.ora Log Parameters

You can set these log parameters in the listener.ora file.

Table 13 listener.ora Log Parameters

listener.ora Parameter Oracle Net Manager Field Description
ADR_BASE_listener_name You must set this parameter manually.

The ADR_BASE_listener_name parameter specifies the base directory for storing which tracing and logging incidents.

Use when DIAG_ADR_ENABLED_listener_name is set to ON.

DIAG_ADR_ENABLED_listener_name You must set this parameter manually.

The DIAG_ADR_ENABLED_listener_name parameter indicates whether ADR tracing is enabled.

When DIAG_ADR_ENABLED_listener_name is set to OFF, non-ADR file tracing is used.

LOG_DIRECTORY_listener_name

LOG_FILE_listener_name

 Log File 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, and the file name is listener.log. These parameters are disabled when ADR_ENABLED is set to ON.

cman.ora Log Parameters

You can set these log parameters in the cman.ora file.

Table 14 cman.ora Log Parameters

cman.ora Parameter Description
ADR_BASE

The ADR_BASE parameter specifies the base directory for storing tracing and logging incidents.

Use this parameter when DIAG_ADR_ENABLED is set to ON.

DIAG_ADR_ENABLED

The DIAG_ADR_ENABLED parameter indicates whether ADR tracing is enabled.

When the DIAG_ADR_ENABLED parameter is set to OFF, non-ADR file tracing is used.

EVENT_GROUP

The event groups that are logged. Multiple events may be designated using a comma-delimited 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 timeouts

  • CMD_PROC: command processing

  • RELAY: events associated with connection control blocks

LOG_DIRECTORY

The destination directory for log files.

By default, the directory is ORACLE_HOME/network/log.

This parameter is disabled when ADR_ENABLED is set to ON.

LOG_LEVEL

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

Setting Logging Parameters in Configuration Files

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

You must manually configure cman.ora file logging parameters.

Setting Parameters for the sqlnet.ora File Using Oracle Net Manager

The following procedure describes how to set the logging parameters in the sqlnet.ora file.

  1. Start Oracle Net Manager.

    See Also: “Using Oracle Net Manager to Configure Oracle Net Services”

  2. In the navigator pane, expand Profile under the Local heading.

  3. From the list in the right pane, select General.

  4. Click the Loggingtab.

  5. Specify the settings.

  6. Choose Save Network Configuration from the File menu.

The name of the log file is sqlnet.log.

Setting Parameters for the listener.ora File Using Oracle Enterprise Manager Cloud Control

The following procedure describes how to set the logging parameters in the listener.ora file using Oracle Enterprise Manager Cloud Control:

  1. Access the Net Services Administration page in Oracle Enterprise Manager Cloud Control.

    See Also: “Using Oracle Enterprise Manager Cloud Control to Configure Oracle Net Services”

  2. Select Listeners from the Administer list, and then select the Oracle home that contains the location of the configuration files.

  3. Click Go to display the Listeners page.

  4. Select a listener, and then click Edit to display the Edit Listeners page.

  5. Click the Logging & Tracing tab.

  6. Specify the settings.

  7. Click OK.

The name of the log file is listener.log.

Setting Parameters for the listener.ora File Using Oracle Net Manager

The following procedure describes how to set the logging parameters in the listener.ora file using Oracle Net Manager:

  1. Start Oracle Net Manager.

    See Also: “Using Oracle Net Manager to Configure Oracle Net Services”

  2. In the navigator pane, expand Listeners under the Local heading.

  3. Select a listener.

  4. From the list in the right pane, select General.

  5. Click the Logging and Tracing tab.

  6. Specify the settings.

  7. Choose Save Network Configuration from the File menu.

The name of the log file is listener.log.

See Also: Oracle Database Net Services Reference

Setting Logging During Control Utilities Runtime

You can set logging during control utility runtime. Setting logging with a control utility does not set parameters in the *.ora files, and the setting is only valid for the control utility session.

The following settings can be set for a control utility:

Note: If the ADR_ENABLED parameter is set to ON, then all logging parameters are set by ADR. Using Oracle Connection Manager to change the parameters will not work.

Related Topics

Using Log Files

This procedure describes how to use a log file to diagnose a network error.

  1. Review the log file for the most recent error number received from the application. This is usually 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 information, then review the next error in the log until you locate the correct error information.

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

Analyzing Listener Logs

The listener log file records information about audit trails, service registration-related events, direct hand-off events, subscriptions for Oracle Notification Service (ONS) node-down events, and Oracle Clusterware notifications.

Listener Log Audit Trails

The audit trail information in the listener log file enables you to analyze network usage statistics, client connection requests, commands issued by the Listener Control utility, and so on.

Listener Log Audit Trail Information

The audit trail information comprises statistics about network usage, client connection requests, and commands issued by the Listener Control utility (such as RELOAD, START, STOP, STATUS, or SERVICES).

You can use the audit trail information to view trends and user activity by first storing it in a table and then collating it in 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

This is the format in which audit trail text fields are captured in the listener log file.

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

Properties of the audit trail are:

Example 16-4 shows a log file excerpt with RELOAD command request.

Example 16-4 Listener Log Event for Successful RELOAD Request

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

Example 16-5 shows a log file excerpt with a successful connection request.

Example 16-5 Listener Log Events for a Successful Connection Request

14-MAY-2012 15:28:58 *
(connect_data=(service_name=sales.us.example.com)(cid=(program=)(host=sales-server)
(user=jdoe)))
* (address=(protocol=tcp)(host=192.0.2.35)(port=41349)) * establish
* sales.us.example.com * 0

Example 16-6 shows a log file excerpt with a successful execution of the STATUS command by host sales-server. It is followed by an unsuccessful connection attempt by a client with an IP address of 192.0.2.35. This connection attempt resulted in an ORA-12525: Listener Has Not Received Client’s Request in Time Allowed error message. This error occurs when a client fails to complete its connection request in the time specified by the INBOUND_CONNECT_TIMEOUT_listener_name parameter in the listener.ora file. This client could be attempting a denial-of-service attack on the listener.

Example 16-6 Listener Log Events for an Unsuccessful Connection Request

03-MAY-2012 16:41:57 *
(CONNECT_DATA=(CID=(PROGRAM=)(HOST=sales-server)(USER=jdoe))(COMMAND=status)
(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=153092352)) * status * 0
03-MAY-2012 16:42:35 * <unknown connect data> *
(ADDRESS=(PROTOCOL=tcp)(HOST=192.0.2.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

Related Topics

Listener Service Registration Events

The service registration events information in the listener log file enables you to analyze registration-related statistics, such as service names for instances, instance names, service handlers, load information, dynamic listening endpoints, and so on.

Listener Service Registration Event Information

The service registration information comprises statistics related to database service registration events, such as service_register, service_update, and service_died.

During service registration, the Listener Registration (LREG) process provides the listener with information about the following:

The recorded service registration-related events mentioned in the following table are listed in the listener.log file:

Table 15 Service Registration Event Log Information

Event Description
service_register Registration information that the listener receives for an instance.
service_update Updated registration information that the listener receives for a particular instance, such as dispatcher or instance load information.
service_died Lost connection information for the connections that the listener is unable to establish with LREG. All registration information for the instance is discarded. Clients are unable to connect to the instance until LREG registers it again.

Format of the Listener Service Registration Information

This is the format for database service registration event messages captured in the listener log file.

Timestamp * Event *  Instance Name * Return Code

Properties of service registration fields are:

Example 16-7 shows a log file with service registration events. 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.

Example 16-7 Listener Log with Service Registration Events

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

Related Topics

Listener Direct Hand-Off Information

The direct hand-off information in the listener log file enables you to analyze 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:

The following example shows a direct hand-off event in the log file.

Example 16-8 Listener Log Event for Direct Hand-Off

21-MAY-2012 10:54:55 * oracle.aurora.net.SALESHttp2 * handoff * 0

Listener Subscription for ONS Node-Down Event Information

The listener subscribes to the Oracle Notification Service (ONS) node-down event on startup if the ONS configuration file is available. The ONS node-down event information in the listener log file enables you to analyze these messages.

The 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 is recorded to the listener log file on each STATUS command if the subscription has not completed, such as the ONS daemon is not running on the host.

WARNING: Subscription for node down event still pending

The listener cannot receive the ONS event while subscription is pending. Other than that, no other listener functionality is affected.

Listener Oracle Clusterware Notification Information

If the required Oracle Clusterware libraries are installed and Oracle Clusterware is started on the host, then the listener notifies Oracle Clusterware about its status during start and stop processes. The Oracle Clusterware notification information in the listener log file enables you to analyze these messages.

After a successful notification to Oracle Clusterware (shown as CRS in the following log messages), listeners record the event in the log. No message is 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 (CMAN) generates the cman_alias.log file in the specified log directory. This log file records messages related to the CMAN listener, gateway, CMADMIN processes, and alerts.

The alert log entry is a chronological list of all critical errors. In addition to logging critical errors, it captures information about instance startup and shutdown. It also records values of all configuration parameters at the beginning and end of a session.

Each log entry consists of a timestamp and an event. You can configure the cman.ora file to log events for the following categories:

Use the SET EVENT command to specify the type of events that you want to log.

Table 16 CMADMIN and Gateway Log Entry Details

Log Entry Event Description
CMADMIN Failed to get procedure ID The CMCTL session connected to CMADMIN has disconnected.
CMADMIN GMON attributes validated Informational message. The parameters needed for CMADMIN to come up are specified correctly.
CMADMIN Invalid connect data An unknown client is trying to connect to CMADMIN. This is most likely a denial of service attack.
CMADMIN No connect data An unknown client is trying to connect to CMADMIN. This is most likely a denial of service attack.
Gateway Connected to monitor The gateway has connected to CMADMIN.
Gateway Housekeeping Informational message. Internal housekeeping for the gateway process is in order. The gateway process is properly connected to the CMADMIN process.
Gateway Idle timeout The connection is disconnected because it was idle longer than the time specified in the cman.ora file.
Gateway Out of connection control block (CCB)

CMADMIN cannot 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 Session timeout The connection is disconnected because it exceeded the session timeout specified in the cman.ora file.
Gateway State change from Empty to Init State change message from the gateway. After it reaches the Init state, the gateway begins some internal data initialization.
Gateway State change from Init to Ready State change message from the gateway. After it reaches the Ready state, the gateway begins accepting connections from the client.

Example 16-9 Sample CMADMIN Log Messages

-------------------------------
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:46:40)(EVENT=Parameter list)
    (listener_address=(address=(protocol=tcp)(host=sales1)(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)
    (trace_directory=/home/user/network/admin/log)
    (trace_level=off)
    (trace_timestamp=OFF)
    (trace_filelen=0)
    (trace_fileno=0)
)
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:46:40)(EVENT=Shared Memory Size)
(BYTES=82524))
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:46:40)(EVENT=GMON Attributes validated)
(Type=Information))
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:46:40)(EVENT=NS Listen Successful)
((ADDRESS=(PROTOCOL=tcp)(HOST=sales1)(PORT=1574))))
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:46:44)(EVENT=Received command)(CMD=verify
password))
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:46:44)(EVENT=Received command)
(CMD=version))
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:46:44)(EVENT=Received command)
(CMD=show status))
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:46:44)(EVENT=Failed to get procedure id))
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:49:12)(EVENT=Received command)(CMD=verify
password))
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:49:15)(EVENT=Failed to get procedure id))
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:49:29)(EVENT=Received command)(CMD=verify
password))
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:49:46)(EVENT=Failed to get procedure id))
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:49:50)(EVENT=Received command)(CMD=verify
password))
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:49:50)(EVENT=Received command)
(CMD=probe monitor))
(LOG_RECORD=(TIMESTAMP=08-MAY-2022 08:49:50)(EVENT=Received command)
(CMD=shutdown normal))
-------------------------------

Example 16-10 Sample Gateway Log Messages

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

Related Topics

Tracing Error Information for Oracle Net Services

Tracing produces a detailed sequence of statements that describe network events as they are run. Tracing an operation enables you to obtain more information about 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.

Note: 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.

Understanding Oracle Net Services Trace File Names

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

Table 17 Trace Files Names

Trace File Component
instance-name_pid.trc Oracle Connection Manager listener
instance-name_cmgw_pid.trc Oracle Connection Manager CMGW process
instance-name_cmadmin_pid.trc Oracle Connection Manager CMADMIN 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, and the location where the files are stored, are set in the configuration file of each network component as described in Table 16-18.

Table 18 Location of Trace Parameters

Configuration File Component
cman.ora Oracle Connection Manager processes
listener.ora Listener
sqlnet.ora

Client

Database server

TNSPING utility

This section contains the following topics:

See Also: Oracle Database Net Services Reference for additional information about these parameters

cman.ora Trace Parameters

Review the trace parameter settings for Oracle Connection Manager that can be set in the cman.ora file.

Table 19 cman.ora Trace Parameters

cman.ora Parameter Description
TRACE_DIRECTORY

The destination directory for trace files.

By default, the directory is ORACLE_HOME/network/trace.

TRACE_FILELEN The size of the trace file in KB. When the size is reached, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO parameter.
TRACE_FILENO

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, 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, then 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

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 one of the following values:

  • 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 by Oracle Support Services.

The Oracle Connection Manager listener, gateway, and CMADMIN processes create trace files on both Linux and Microsoft Windows.

TRACE_TIMESTAMP If the TRACING parameter is enabled, then a time stamp in the form of dd-mon-yyyy hh:mi:ss:mil is created for every trace event in the listener trace file.

listener.ora Trace Parameters

Review the trace parameter settings for the listener that can be set in the listener.ora file.

Table 20 listener.ora Trace Parameters

listener.ora Parameter Oracle Enterprise Manager Cloud Control/Oracle Net Manager Field Description
TRACE_LEVEL_listener_name Select a trace level/Trace Level

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 one of the following values:

  • 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 by Oracle Support Services.

TRACE_DIRECTORY_listener_name

TRACE_FILE_listener_name

 Trace File The destination directory and file for the trace file. By default, the directory is ORACLE_HOME/network/trace, and the file name is listener.trc.
TRACE_FILEAGE_listener_name You must set this parameter manually. The maximum age of listener trace files in minutes. When the age limit is reached, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_listener_name parameter.
TRACE_FILEAGE_SERVER You must set this parameter manually. Specifies the maximum age of server trace files in minutes. When the age limit is reached, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_SERVER parameter.
TRACE_FILELEN_listener_name You must set this parameter manually. The size of the listener trace files in KB. When the size is reached, 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 You must set this parameter manually.

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, 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, then 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.

When this parameter is set with the TRACE_FILEAGE_listener_name parameter, trace files are cycled based on the age of the trace file. The first file is used until the age limit is reached, then the second file is use, and so on. When the last file's age limit is reached, the first file is re-used, and so on.

When this parameter is set with both the TRACE_FILELEN_listener_name and TRACE_FILEAGE_listener_name parameters, trace files are cycled when either the size limit or the age limit is reached.

TRACE_TIMESTAMP_listener_name You must set this parameter manually. A time stamp in the form of dd-mon-yyyy hh:mi:ss:mil for every trace event in the listener trace file.

sqlnet.ora Trace Parameters

Review the trace parameter settings that can be set in the sqlnet.ora file.

Table 21 sqlnet.ora Trace Parameters

sqlnet.ora Parameter Oracle Net Manager Field Description
TRACE_DIRECTORY_CLIENT Client Information: Trace Directory The destination directory for the client trace output. By default, the client directory is ORACLE_HOME/network/trace.
TRACE_DIRECTORY_SERVER Server Information: Trace Directory The destination directory for the database server trace output. By default, the server directory is ORACLE_HOME/network/trace.
TRACE_FILE_CLIENT Client Information: Trace File 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 The name of the trace file for the database server. By default the trace file name is svr_pid.trc.
TRACE_FILEAGE_CLIENT You must set this parameter manually. Specifies the maximum age of client trace files in minutes. When the age limit is reached, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_CLIENT parameter.
TRACE_FILEAGE_SERVER You must set this parameter manually. Specifies the maximum age of server trace files in minutes. When the age limit is reached, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_SERVER parameter.
TRACE_FILELEN_CLIENT You must set this parameter manually. The size of the client trace files in KB. When the size is reached, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_CLIENT parameter.
TRACE_FILELEN_SERVER You must set this parameter manually. The size of the database server trace files in KB. When the size is reached, the trace information is written to the next file. The number of files is specified with the TRACE_FILENO_SERVER parameter.
TRACE_FILENO_CLIENT You must set this parameter manually.

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, 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, then 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.

When this parameter is set with the TRACE_FILEAGE_CLIENT parameter, trace files are cycled based on the age of the trace file. The first file is used until the age limit is reached, then the second file is use, and so on. When the last file's age limit is reached, the first file is re-used, and so on.

When this parameter is set with both the TRACE_FILELEN_CLIENT and TRACE_FILEAGE_CLIENT parameters, trace files are cycled when either the size limit or age limit is reached.

TRACE_FILENO_SERVER You must set this parameter manually.

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, 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, then 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.

When this parameter is set with the TRACE_FILEAGE_SERVER parameter, trace files are cycled based on the age of the trace file. The first file is used until the age limit is reached, then the second file is use, and so on. When the last file's age limit is reached, the first file is re-used, and so on.

When this parameter is set with both the TRACE_FILELEN_SERVER and TRACE_FILEAGE_SERVER parameters, trace files are cycled when either the size limit or age limit is reached.

TRACE_LEVEL_CLIENT Client Information: Trace Level

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 one of the following values:

  • 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 by Oracle Support Services.

TRACE_LEVEL_SERVER Server Information: Trace Level

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 one of the following values:

  • 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 by Oracle Support Services.

TRACE_TIMESTAMP_CLIENT You must set this parameter manually. A time stamp in the form of dd-mon-yyyy hh:mi:ss:mil for every trace event in the client trace file, sqlnet.trc.
TRACE_TIMESTAMP_SERVER You must set this parameter manually. A time stamp in the form of dd-mon-yyyy hh:mi:ss:mil for 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, and 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 TNSPING utility tracing parameters described in Table 16-22 to the sqlnet.ora file. The TNSPING utility determines whether a service, such as a database or other TNS services on an Oracle Net network can be successfully reached.

Table 22 TNSPING Trace Parameters

sqlnet.ora Parameter Description
TNSPING.TRACE_DIRECTORY The destination directory for TNSPING trace file, tnsping.trc. By default, the directory is ORACLE_HOME/network/trace.
TNSPING.TRACE_LEVEL

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 one of the following values:

  • 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 by Oracle Support Services.

Setting Tracing Parameters in Configuration Files

Configure tracing parameters for the sqlnet.ora file with Oracle Net Manager and listener.ora file with either Oracle Enterprise Manager Cloud Control or Oracle Net Manager. You must manually configure cman.ora file tracing parameters.

Setting Tracing Parameters for sqlnet.ora File Using Oracle Net Manager

The following procedure describes how to set the tracing parameters for the sqlnet.ora file using Oracle Net Manager:

  1. Start Oracle Net Manager.

    See Also: “Using Oracle Net Manager to Configure Oracle Net Services”

  2. In the navigator pane, expand Profile under the Local heading.

  3. From the list in the right pane, select General.

  4. Click the Tracingtab.

  5. Specify the settings.

  6. Choose Save Network Configuration from the File menu.

The name of the trace file for the client is sqlnet.trc. The name of the trace file for the server is svr_pid.trc.

Setting Tracing Parameters for the Listener Using Oracle Enterprise Manager Cloud Control

The following procedure describes how to set the tracing parameters for the listener using Oracle Enterprise Manager Cloud Control:

  1. Access the Net Services Administration page in Oracle Enterprise Manager Cloud Control.

    See Also: “Using Oracle Enterprise Manager Cloud Control to Configure Oracle Net Services”

  2. SelectListeners from the Administer list, and then select the Oracle home that contains the location of the configuration files.

  3. Click Go to display the Listeners page.

  4. Select a listener, and then click Edit to display the Edit Listeners page.

  5. Click the Logging & Tracing tab.

  6. Specify the settings.

  7. Click OK.

The name of the trace file is listener.trc.

Setting Tracing Parameters for the Listener Using Oracle Net Manager

The following procedure describes how to set the tracing parameters for the listener using Oracle Net Manager:

  1. Start Oracle Net Manager.

    See Also: “Using Oracle Net Manager to Configure Oracle Net Services”

  2. In the navigator pane, expand Listeners from the Local heading.

  3. Select a listener.

  4. From the list in the right pane, select General.

  5. Click the Logging and Tracing tab.

  6. Specify the settings.

  7. Choose Save Network Configuration from the File menu.

Setting Tracing During Control Utilities Runtime

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:

Evaluating Oracle Net Services Trace Files

Trace files can help Oracle Support Services diagnose and troubleshoot network problems. This section explains how to perform basic analysis of trace files.

Flow of Data Packets Between Network Nodes

Oracle Net performs its functions by sending and receiving data packets. You can view the actual contents of the Oracle Net packet in your trace file by specifying a trace level of support. The order of the packet types sent and received help to determine how the 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.

Each packet has a keyword that denotes the packet type. All packet types begin with the prefix “nsp”. This is helpful when reviewing trace files for specific packet information. The following keywords are used in a trace file:

Example 16-11 shows typical packet information. In the example, the nscon procedure sends an NSPTCN packet over the network.

Example 16-11 Packet Information

nscon: entry
nscon: doing connect handshake...
nscon: sending NSPTCN packet
nspsend: entry
nspsend: plen=187, type=1
nspsend: 187 bytes to transport
nspsend:packet dump
nspsend:00 BB 00 00 01 00 00 00  |........|
nspsend:01 33 01 2C 0C 01 08 00  |.3.,....|
nspsend:7F FF 7F 08 00 00 00 01  |........|
nspsend:00 99 00 22 00 00 08 00  |..."....|
nspsend:01 01 28 44 45 53 43 52  |..(DESCR|
nspsend:49 50 54 49 4F 4E 3D 28  |IPTION=(|
nspsend:43 4F 4E 4E 45 43 54 5F  |CONNECT_|
nspsend:44 41 54 41 3D 28 53 49  |DATA=(SI|
nspsend:44 3D 61 70 33 34 37 64  |D=ap347d|
nspsend:62 31 29 28 43 49 44 3D  |b1)(CID=|
nspsend:28 50 52 4F 47 52 41 4D  |(PROGRAM|
nspsend:3D 29 28 48 4F 53 54 3D  |=)(HOST=|
nspsend:61 70 32 30 37 73 75 6E  |sales-12|
nspsend:29 28 55 53 45 52 3D 6D  |)(USER=m|
nspsend:77 61 72 72 65 6E 29 29  |scott))|
nspsend:29 28 41 44 44 52 45 53  |)(ADDRES|
nspsend:53 5F 4C 49 53 54 3D 28  |S_LIST=(|
nspsend:41 44 44 52 45 53 53 3D  |ADDRESS=|
nspsend:28 50 52 4F 54 4F 43 4F  |(PROTOCO|
nspsend:4C 3D 74 63 70 29 28 48  |L=tcp)(H|
nspsend:4F 53 54 3D 61 70 33 34  |OST=sale|
nspsend:37 73 75 6E 29 28 50 4F  |s-12)(PO|
nspsend:52 54 3D 31 35 32 31 29  |RT=1521)|
nspsend:29 29 29 00 00 00 00 00  |))).....|
nspsend: normal exit
nscon: exit (0)

Pertinent Oracle Net Trace Error Output

When there is a problem, the error code is logged in the trace file. Example 16-12 illustrates typical trace file output for a failed SQL*Plus connection to a database server. The error message and error stack are shown in bold.

Example 16-12 Trace Example

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

Note: In the error stack in the preceding example, an operating system error code is shown. Each operating system has its own error codes, refer to your system documentation for information about operating system error codes.

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 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 Example 16-12:

[22-MAY-2012 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

In the preceding example, the main TNS error is 12537, and its secondary error is

  1. The protocol adapter error is 507. Using oerr, you can find out more information about return codes 12537, 12560, and 507. User input is shown in bold in the following examples.
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 12560
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.

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 understand the information provided in trace files by converting existing lines of trace file text into a more readable paragraph. The Trace Assistant works only with level 16 (support) Oracle Net Services trace files. Note: The Trace Assistant can only be used when the DIAG_ADR_ENABLED parameter is set to off. See “Understanding Automatic Diagnostic Repository”.

Trace Assistant Syntax

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

trcasst [options] filename

The options are described in Table 16-23.

Table 23 Trace Assistant Syntax

Option Description
-elevel

Displays error information. After the -e, use 0, 1, or 2 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 is processed.

-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, which provides detailed connectivity and TTC events, error level zero (0), and statistics in the trace file. Example 16-13 shows how the Trace Assistant converts the trace file information into a more readable format using the -e1 option.

Example 16-13 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 enables you to view data packets from both the Oracle Net and TTC communication layers.

You can view the packets using the following options:

Example 16-14 shows summary information from the -oc option.

Example 16-14 Summary Information from 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.example.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.example.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                      *
    *************************************************************************

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, and received by the database server or listener. Example 16-15 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-15 Detailed Information from 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:8192
      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.example.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:8192
      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.example.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: 8192
      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: DAABBCEF0003000000040004000100010002
            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: DAABBCEF00030000000200040001
            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 (TTC) 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 log on, then a response is returned from the database server that the request was completed.

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.

Output is displayed in the following format:

description TTC_message cursor_number SQL_statement bytes_sent bytes_received

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

Example 16-16 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                      *
    *************************************************************************

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

Example 16-17 Detailed TTC Information from trcasst -ot Output

    *************************************************************************
    *                        Trace  Assistant                                  *
    *************************************************************************

Set protocol (TTIPRO)
        Operation 01 (con) Send protocol version=6
        Originating platform: x86_64/Linux 2.4.xx

Set protocol (TTIPRO)
        Operation 01 (con) Receive protocol version=6
        Destination platform: x86_64/Linux 2.4.xx

Set datatypes (TTIDTY)

Set datatypes (TTIDTY)

Start of user function (TTIFUN)
        Get the session key (OSESSKEY)

Return opi parameter (TTIRPA)

Start of user function (TTIFUN)
        Generic authentication call (OAUTH)

Return opi parameter (TTIRPA)

Piggyback function follows (TTIPFN)
Start of user function (TTIFUN)
        V8 session switching piggyback (O80SES)
Start of user function (TTIFUN)
        Get Oracle version/date (OVERSION)

Return opi parameter (TTIRPA)
Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - 64bit Production
 Version 18.1.0.0.0
Start of user function (TTIFUN)
        New v8 bundled call (OALL8) Cursor # 0
 Parse Fetch



Describe information (TTIDCB)

Start of user function (TTIFUN)
        Fetch row (OFETCH) Cursor # 3

ORACLE function complete (TTIOER)
ORA-01403: no data found


Piggyback function follows (TTIPFN)
Start of user function (TTIFUN)
        Cursor Close All (OCCA)
Start of user function (TTIFUN)
        New v8 bundled call (OALL8) Cursor # 0
 Parse Fetch



Describe information (TTIDCB)

Piggyback function follows (TTIPFN)
Start of user function (TTIFUN)
        Cursor Close All (OCCA)
Start of user function (TTIFUN)
        New v8 bundled call (OALL8) Cursor # 0
 Parse Fetch



Describe information (TTIDCB)

Piggyback function follows (TTIPFN)
Start of user function (TTIFUN)
        Cursor Close All (OCCA)
Start of user function (TTIFUN)
        New v8 bundled call (OALL8) Cursor # 0
 !Keep Parse



Sending the I/O vector only for fast upi (TTIIOV)

Piggyback function follows (TTIPFN)
Start of user function (TTIFUN)
        Cursor Close All (OCCA)
Start of user function (TTIFUN)
        New v8 bundled call (OALL8) Cursor # 0
 Parse Fetch



Describe information (TTIDCB)

Piggyback function follows (TTIPFN)
Start of user function (TTIFUN)
        Cursor Close All (OCCA)
Start of user function (TTIFUN)
        Commit (OCOMMIT)

V6 Oracle func complete (TTISTA)


Start of user function (TTIFUN)
        Commit (OCOMMIT)

V6 Oracle func complete (TTISTA)


Start of user function (TTIFUN)
        Logoff off of Oracle (OLOGOFF)
        MAXIMUM OPEN CURSORS: 0
        CURSORS NOT CLOSED: 0


V6 Oracle func complete (TTISTA)
        Succeeded

    *************************************************************************
    *                    Trace Assistant has completed                      *
    *************************************************************************

Example 16-18 shows detailed SQL information from the -ouq option. 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 been 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:

Example 16-18 Detailed SQL Information from 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                      *
    *************************************************************************

Connection Example

These are the sample outputs using the trcasst -la and -li options.

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

Example 16-19 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.example.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.example.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.example.com)(CID=(PROGRAM=)(HOST=sales-server)
        (USER=oracle))))
    *************************************************************************
    *                    Trace Assistant has completed                      *
    *************************************************************************

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

Example 16-20 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: 8192
        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.example.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: 8192
        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: DAABBCEF0003000000040004000100010002
                 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: DAABBCEF00030000000200040001
                 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 the number of TTC calls, packets, and bytes sent and received between the network partners. Example 16-21 shows typical trace file statistics from the -s option.

Example 16-21 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

Some messages recommend contacting Oracle Support Services to report a problem. When you contact Oracle Support Services, have the following information available:

You will also be expected to provide the following: