Questions and Answers

Setting Events

?

Event syntax

20 May 1999

Is there a limit on how many events one can set? I set the following in our init.ora and I was unable to restart my database.

event = "10262 trace name context forever level 2000"
event = "600 trace library_cache level 10"

 
? You can set multiple events in the init.ora file, but they may only have comments or white space between them, not other parameter settings. Otherwise the earlier event setting(s) will be replaced by the later, rather than supplemented by them.

In your case, however, the problems relate to the syntax of your event settings. You need a , between the FOREVER and LEVEL keywords as follows:

event = "10262 trace name context forever, level 2000"

You also need the NAME keyword before the dump name in the second event setting, and you may want the FOREVER keyword there too. Without the FOREVER keyword, the event setting will be deactivated after it has fired once. Try this:

event = "600 trace name library_cache forever, level 10"

 
 
?

Events 10231 and 10232

4 July 1999

I'm looking for some help in understanding events 10231/10232 in the init.ora parameter file.
 
? Event 10231 causes full table scans to skip corrupt blocks, rather than fail with an ORA-1578 error. Event 10232 causes the corrupt blocks to be dumped to the process trace file. If you have found these events set in your parameter file, they are probably left over from a time when somebody suspected a data block corruption and set these events prior to doing a full table scan to check it out. If you are thinking of setting them yourself to investigate something, then setting them at the session level should be adequate.
 
 
?

Event documentation

12 October 1999

Do you know where I can find documentation on the various events?
 
? There is no formal documentation. However, the $ORACLE_HOME/rdbms/mesg/oraus.msg file on Unix contains a brief description of many of the numeric events. Look in the range from 10000 to 10999.
 
 
?

Event 10046

3 November 1999

I don't understand what "event 10046, level 8" is?
 
? Event 10046 is a widely used superset of sql_trace. The syntax for the parameter file setting is

event = "10046 trace name context forever, level 8"

The syntax for a single session is

alter session set events '10046 trace name context forever, level 8';

Have a play with it and get familiar with the output. It is a very valuable tuning/diagnostic tool. See the excellent Oracle Note 39817.1 for a detailed explanation of the information in the trace file.

 
 
?

alter session set sql_trace

5 November 1999

V$PARAMETER still shows sql_trace as being set to FALSE, even after it has been explicitly set to TRUE using ALTER SESSION. Why?
 
? The answer is that it does not really change the parameter. It sets an event that is equivalent. If you use the which_events.sql script, you should see that event 10046 is set at level 1.
 
 
?

Events for Oracle Applications

20 January 2000

I have recently installed Oracle Applications and I came across the folllowing events in my init.ora file. 
event = "10210 trace name context forever, level 2"
event = "10211 trace name context forever, level 2"
event = "10235 trace name context forever, level 1"
event = "10246 trace name context forever, level 2"
event = "7267 trace name errorstack level 4"
event = "3106 trace name errorstack level 4"
event = "10076 trace name context forever, level 1"
I am quite confused about all these events and levels. Can you help me?
 
? Ask Oracle for an explanation. However, I think that these events except 10076 should all be switched off. Event 10235, in particular, is very bad for performance.
 
 
?

Event numbers

9 March 2000

Are the event numbers listed in the $ORACLE_HOME/rdbms/mesg/oraus.msg file (between 10000 and 10999) all the events that there are, or are there other events that are not listed?
 
? Yes, there are other events. For example, event 10901 (to disable extent trimming) is not listed. There are also some events outside that number range that are listed, such as 29700 (to enable the collection of DLM lock conversion statistics), so there could well be others outside the normal range that are not listed too.
 
 
Copyright © Ixora Pty Ltd Send Email Home