16.7.5.1 Trace Assistant Syntax

To run the Trace Assistant, enter the trcasst command at the command line.

trcasst [options] filename

Table 16-24 Trace Assistant Syntax Options

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.

The following example shows how the Trace Assistant converts the trace file information into a more readable format using the -e1 option.

Example 16-15 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:Cannot connect. No listener at %s."  
 //  *Cause: The connection request could not be completed because either the 
 //   database listener process was not running on the specified host 
 //   and port, or an Interprocess Communication (IPC) protocol 
 //   connection was attempted but there was no listener for the 
 //   specified key running on the local machine. PL/SQL applications
 //   using UTL packages can also get this error if the external server
 //   process is not listening on the specified address. 
 // *Action: 
 //  - If the error shows the host and port that the connection tried to 
 //    use, then ensure that a listener process is running on that host 
 //    and is listening on that port. If the message indicates that there 
 //    was no listener at the specified key, then ensure that the listener 
 //    is running on the local machine and listening for the specified 
 //    key. The listener process is used to initially handle all 
 //    connections to Oracle Database.
 //  - Check for mistakes in the specified connection string.
 //  - If you are using an alias from a tnsnames.ora file, then verify 
 //    the correctness of the host and port. Alternatively, verify the 
 //    correctness of the key if you are using an IPC connection.
 //  - If using an Easy Connect connection string, then ensure that the 
 //    host and port are correct. 
 //  - Use lsnrctl to check that the listener is running and to verify 
 //    the port or key it listens to. Run one of the following:
 //      * lsnrctl status
 //      * Or, when a listener is named in the listener.ora file, run:
 //                 lsnrctl status <listener_name>
 //      * Or, if an Oracle Connection Manager (Oracle CMAN) proxy 
 //                 listener is named in the cman.ora file, run:
 //                 cmctl show status -c <cman_name>
 / 
12560, 00000 "TNS:Database communication protocol error." 
 //  *Cause: A lower level communication protocol adapter error occurred. 
 //  *Action: 
 //  - Check for lower level network transport errors in the error stack
 //    for additional information.
 //  - Ensure the protocol specification used in the address for the
 //    connection is correct.
 //  - For further details, turn on network tracing and rerun the
 //    operation. Turn off tracing when the operation is complete.
 //  - Contact Oracle Support.
 / 
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.