Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: need help on INIT.ORA event=

Re: need help on INIT.ORA event=

From: Viacheslav Leichinsky <v_leichinsky_at_hotmail.com>
Date: 2000/05/03
Message-ID: <8eou4h$h1m$1@nnrp1.deja.com>#1/1

In article <390FBBA5.68C1DF70_at_prodigy.net>,   "Mr. Rovin" <mr.rovin_at_prodigy.net> wrote:
>
> I need some documentation on those accursed event = parameters that
 turn
> up in INT.ORA. We are in a very government-regulated environment, and
> we can't casually change system paramters without documentation on
 what
> we are doing. A 3rd-party vendor wants us to add
>
> event = (412 trace name error stack)
>
> to our INIT.ORA, which they don't understand, and they say they got it
> verbally from Oracle technical support. I can't find anything useful

Possible it's usefull
(I found this one in Revealnet Oracle Knowledge Base):

.....................................

EVENT Modifies the scope of ALTER SESSION SET EVENTS commands so that they pertain to an entire instance, instead of to a single session. This is usually only used for testing and, as with undocumented initialization parameters, these should only be used under the direction of a senior level DBA or Oracle support.

To get an error stack related to a SQLNET ORA-03120 error:

event="3120 trace name error stack"

To enable block header and trailer checking to detect corrupt blocks:

event="10210 trace name context forever, level 10" -- for tables event="10211 trace name context forever, level 10" -- for indexes

and to go with these the undocumented parameter setting:

 _db_block_cache_protect=TRUE

which will prevent corruption from getting to your disks (at the cost of a database crash)

For tracing of a MAX_CURSORS exceeded error:

event="1000 trace name ERRORSTACK level 3"

To turn on bitmapped indexes in 7.3.2:

event="10111 trace name context forever"
event="10112 trace name context forever"
event="10114 trace name context forever"

andåset the initialization parameter COMPATIBLE to 7.3.2

To work around a space leak problem:

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

To trace memory shortages:

event="10235 trace name context forever, level 4" event="600 trace name heapdump, level 4"

.............

Slava.

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Wed May 03 2000 - 00:00:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US