Database Reference
In-Depth Information
WAIT #2: nam='SQL*Net message from client' ela= 233116 driver id=1413697536 #bytes=1
p3=0 obj#=-1 tim=392103895174
*** ACTION NAME:() 2007-10-30 22:53:04.281
*** MODULE NAME:() 2007-10-30 22:53:04.281
*** CLIENT ID:() 2007-10-30 22:53:04.281
STAT #2 id=1 cnt=1 pid=0 pos=1 obj=0 op='FAST DUAL (cr=0 pr=0 pw=0 time=14 us)'
=====================
PARSING IN CURSOR #2 len=63 dep=0 uid=61 oct=3 lid=61 tim=392103896865 hv=2359234954
ad='672f1af4'
SELECT 'application instrumentation settings removed' FROM dual
END OF STMT
The fact that the module and action names appear before the
SELECT
statement, which
retrieves the session identifier, proves that the instrumentation settings were piggybacked with
the network packet(s) sent to parse the
SELECT
statement. JDBC end-to-end metrics do not
cause additional network round-trips. At the IP level, the extra data may necessitate an addi-
tional packet, but there will be no extra round-trips reported as the wait event
SQL*Net message
from client
.
Using TRCSESS
TRCSESS is a new utility that ships with Oracle10
g
and subsequent releases. It may be used to
extract relevant sections from one or more trace files into a single file based on the following
criteria:
Service name
V$SESSION.SERVICE_NAME
)
Session identification (
V$SESSION.SID
and
V$SESSION.SERIAL#
)
Module name
V$SESSION.MODULE
)
Action name (
V$SESSION.ACTION
)
Client identifier (
V$SESSION.CLIENT_IDENTIFIER
)
One of the session identification, client identifier, service name, action, and module options
must be specified. If more than a single option is used, the trace file sections that satisfy all the
criteria, are combined into an output file. All the option values are case sensitive. After TRCSESS
has merged the trace information into a single output file, this file may be processed by TKPROF
or the extended SQL trace profiler ESQLTRCPROF included with this topic.
The TRCSESS utility prints information on its usage when it is called without any arguments.
$ trcsess
trcsess [output=<output file name >] [session=<session ID>] [clientid=<clientid>]
[service=<service name>] [action=<action name>] [module=<module name>]
<trace file names>
output=<output file name> output destination default being standard output.
session=<session Id> session to be traced.
Session id is a combination of session Index & session serial number e.g. 8.13.
