Database Reference
In-Depth Information
Application Instrumentation Entries in Oracle9
i
Running the same instrumentation code as in the section “Application Instrumentation Entries
in Oracle10
g
and Oracle11
g
” against Oracle9
i
results in far fewer entries being written to the
trace file. The instance service name is neither available in
V$SESSION
nor in the trace file. An
Oracle9
i
trace file contains lines such as these:
*** SESSION ID:(10.697) 2007-08-31 18:19:10.000
APPNAME mod='mod' mh=781691722 act='act' ah=3947624709
Obviously, the format for module and action is different in Oracle9
i
. Module and action
are always logged on a single line after the keyword
APPNAME
, even when just the action is set
with
DBMS_APPLICATION_INFO.SET_ACTION
. Abbreviations used in the
APPNAME
entry are explained in
Table 24-16.
7
Table 24-16.
Oracle9i APPNAME Parameters
Parameter
Meaning
mod
Module; corresponds to
V$SESSION.MODULE
mh
Module hash value; corresponds to
V$SESSION.MODULE_HASH
act
Action; corresponds to
V$SESSION.ACTION
ah
Action hash value; corresponds to
V$SESSION.ACTION_HASH
In Oracle9
i
, the client identifier is not written to the trace file. It is merely set in
V$SESSION.CLIENT_IDENTIFIER
.
7
SQL> SELECT client_identifier FROM v$session WHERE sid=10;
CLIENT_IDENTIFIER
----------------------------------------------------------
ndebes@WORKGROUP\DBSERVER
ERROR Entry Format
Errors during execution of SQL statements are marked by
ERROR
entries. These may occur for
statements that were parsed successfully, but failed to execute successfully. The minimum SQL
trace level for
ERROR
entries is 1. Here is an example:
PARSING IN CURSOR #6 len=94 dep=0 uid=30 oct=2 lid=30 tim=171868250869 hv=3526281696
ad='6778c420'
INSERT INTO poem (author, text) VALUES(:author, empty_clob())
RETURNING ROWID INTO :row_id
END OF STMT
PARSE #6:c=0,e=150,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,tim=171868250857
EXEC #6:c=10014,e=52827,p=0,cr=2,cu=5,mis=0,r=0,dep=0,og=1,tim=171868303859
ERROR #6:err=372 tim=17186458
7. Strangely, the IP address was silently truncated from the client identifier by the Oracle 9.2.0.1.0
instance used.
