oracleevent相关操作.doc

oracle事件及相关操作介绍 Introduction There are four types of numeric events Immediate dumps Conditional dumps Trace dumps Events that change database behaviour Every event has a number which is in the Oracle error message range e.g. event 10046 is ORA-10046 Each event has one or more levels which can be range e.g. 1 to 10 bitmask e.g. 0x01 0x02 0x04 0x08 0x10 flag e.g. 0=off; 1=on identifier e.g. object id, memory address etc Note that events change from one release to another. As existing events become deprecated and then obsolete, the event number is frequently reused for a new event. Note also that the message file sometimes does not reflect the events in the current release. Many events change the behaviour of the database. Some testing events may cause the database to crash. Never set an event on a production database without obtaining permission from Oracle support. In addition, never set an event on a development database without first making a backup. Enabling Events Events can be enabled at instance level in the init.ora file using event=event trace name context forever, level level; Multiple events can be enabled in one of two ways 1 - Use a colon to separate the event text e.g. event = 10248 trace name context forever, level 10:10249 trace name context forever, level 10 2 - List events on consecutive lines e.g. event = 10248 trace name context forever, level 10 event = 10249 trace name context forever, level 10 Note that in some versions of Oracle, the keyword event must be in the same case (i.e. always uppercase or always lowercase). Events can also be enabled at instance level using the ALTER SYSTEM command ALTER SYSTEM SET EVENTS event trace name context forever, level level; Events are disabled at instance level using ALTER SYSTEM SET EVENTS event trace name context off; Events can also be enabled at session level using the ALTER SESSION command ALTER SESSION SET EVENTS event trace name context fore