What is a database EVENT and how does one set it?
Oracle trace events are useful for debugging the Oracle database server. The
following two examples are simply to demonstrate syntax. Refer to later
notes on this page for an explanation of what these particular events do.
Events can be activated by either adding them to the INIT.ORA parameter
file. E.g.
event='1401 trace name errorstack, level 12'
... or, by issuing an ALTER SESSION SET EVENTS command: E.g.
alter session set events '10046 trace name context forever, level
4';
The alter session method only affects the user's current session, whereas
changes to the INIT.ORA file will affect all sessions once the database has
been restarted.
What database events can be set?
The following events are frequently used by DBAs and Oracle Support to
diagnose problems:
10046 trace name context forever, level 4
Trace SQL statements and show bind variables in trace output.
10046 trace name context forever, level 8
This shows wait events in the SQL trace files
10046 trace name context forever, level 12
This shows both bind variable names and wait events in the SQL trace files
1401 trace name errorstack, level 12
1401 trace name errorstack, level 4
1401 trace name processstate
Dumps out trace information if an ORA-1401 "inserted value too large for
column" error occurs. The 1401 can be replaced by any other Oracle Server
error code that you want to trace.
60 trace name errorstack level 10
Show where in the code Oracle gets a deadlock (ORA-60), and may help to
diagnose the problem.
The following list of events are examples only. They might be version
specific, so please call Oracle before using them:
10210 trace name context forever, level 10
10211 trace name context forever, level 10
10231 trace name context forever, level 10
These events prevent database block corruptions
10049 trace name context forever, level 2
Memory protect cursor
10210 trace name context forever, level 2
Data block check
10211 trace name context forever, level 2
Index block check
10235 trace name context forever, level 1
Memory heap check
10262 trace name context forever, level 300
Allow 300 bytes memory leak for connections
Note: You can use the Unix oerr command to get the description of an event.
On Unix, you can type "oerr ora 10053" from the command prompt to get event
details.
HTH
Ofer
-----Original Message-----
From: Freddie Acosta
[mailto:oracledba-ezmlmshield-x71599355.[Email address protected]
Sent: Wednesday, June 30, 2004 3:59 PM
To: LazyDBA Discussion
Subject: Database event
What is a database EVENT and how does one set it?
Thanks
--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: send a blank email to oracledba-[Email address protected]
By using this list you agree to these
terms:http://www.lazydba.com/legal.html
**********************************************************************
The information contained in this e-mail message may be
privileged and confidential. The information is intended only
for the use of the individual or entity named above. If the
reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying
of this communication is strictly prohibited. If you have
received this communication in error, please notify us
immediately by telephone, or by e-mail and delete the message
from your computer. Thank you!
Unless otherwise stated, any views or opinions expressed in
this e-mail are solely those of the author and do not represent those of
Barak I.T.C (1995) The International Telecommunications Services Corp. Ltd.
**********************************************************************
Oracle LazyDBA home page