Tips by Burleson
When solving tuning problems, session traces are very useful
and offer vital information. Traces are simple and straightforward
for dedicated server sessions, but for shared server sessions,
many processes are involved. The trace pertaining to the user
session is scattered across different trace files belonging to
different processes. This makes it difficult to get a complete
picture of the life cycle of a session.
Now there is a new tool, a command line utility
called trcsess to help read
the trace files. The trcsess command-line utility consolidates
trace information from selected trace files, based on specified
criteria. The criteria include session id, client id, service
name, action name and module name.
Also note that beginning with Oracle 10g, Oracle Trace
functionality is no longer available. For tracing database
activity, use SQLTrace or TKPROF instead.
The syntax for the trcsess utility is:
- output specifies the file where the output is generated.
When this option is not specified, the standard output is used
for the output.
- session consolidates the trace information for the session
specified. The session Id is a combination of session index and
session serial number.
- clientid consolidates the trace information given client Id.
- service consolidates the trace information for the given
- action consolidates the trace information for the given
- module consolidates the trace information for the given
- trace_files is a list of all trace file names, separated by
spaces, in which trcsess will look for trace information. The
wild card character * can be used to specify the trace file
names. If trace files are not specified, all the files in the
current directory are checked by trcsess.