You can look at cumbersome trace files manually, but it is far
better to use the Trace Assistant (trcasst) tool if you are using
SQL*Net database connections. The information in the trace files
will help you to diagnose and troubleshoot network problems by
giving you a better understanding of execution details, but you need
the trcasst tool to display the trace file in readable format!
The trcasst utility will display trace details on these
performance areas:
- The flow of packets between network nodes
- The component of SQL*Net that is failing (listener,
MTS, client, TNS)
Formatting Trace File with the trcasst utility
The Oracle Trace assistant (trcasst) helps us decipher
information contained in the trace files. By using the trcasst
command to translate the raw dump into a more readable trace.
The trcasst utility is very helpful when advanced diagnosis is
required for problem debugging because the trcasst command can be
used to provide a more readable trace.
The trcasst utility is also very helpful when advanced diagnosis
is required for problem debugging.
The trcasst utility provides the following command line
options:
-o - Displays services and TTC (Two Task Common)
information.
Valid trcasst –o options include:
- c - Summary of connection information.
- d - Detailed connection information.
- u - Summary of TTC information.
- t - Detailed TTC information.
- q - SQL commands (used in combination with u).
-e - Displays error information.
Valid trcasst –e t options include:
- 0 - translates NS error numbers.
- 1 - Displays only error translation.
- 2 - Displays error numbers without translation.
l - The –l argument displays services and TTC
information.
Valid trcasst –l include:
- a - trcasst displays data for all connections in trace file.
- i - trcasst displays the trace data for a particular ID from
the –la option.
-s - trcasst displays a summary of statistics.
This includes total bytes sent and received, maximum open
cursors, total calls, parse counts, and more.
If no trcasst options are specified on the command line, the
default for trcasst will be:
trcasst –odt –e0 –s
Sample output generated by the trcasst utility is below.
> trcasst listener.trc Trace
Assistant Utility: Version 9.2.0.1.0 Production on February 6, 2003
9:12: 2 PM
(c) Copyright 2002 Oracle Corporation. All rights
reserved.
*************************************************************************
*
Trace Assistant trcasst *
*************************************************************************
///////////////////////////////////////////////////////////////
Error found.
Error Stack follows:
12537, 00000
"TNS:connection closed"
// *Cause: "End of file" condition
has been reached; partner has disconnected.
// *Action: None
needed; this is an information message.
/
12560, 00000
"TNS:protocol adapter error"
----------------------
Trace File Statistics:
----------------------
Total number
of Sessions: 0
DATABASE:
Operation Count: 0 OPENS, 0
PARSES, 0 EXECUTES, 0 FETCHES
ORACLE NET SERVICES:
Total
Calls : 0 sent, 0 received, 0 oci
Total Bytes : 0 sent, 0
received
Average Bytes: sent per packet, received per packet
Maximum Bytes: 0 sent, 0 received
Grand Total Packets: 0
sent, 0 received
As we see, a raw trace file is far more cryptic than this output
from the trcasst utility.
See these links for more information of tracing Oracle activity:
 |
|
Get the Complete
Oracle SQL Tuning Information
The landmark book
"Advanced Oracle
SQL Tuning The Definitive Reference" is
filled with valuable information on Oracle SQL Tuning.
This book includes scripts and tools to hypercharge Oracle 11g
performance and you can
buy it
for 30% off directly from the publisher.
|
