TAGS
Session altered.
You see I have combined 3 options to the action, level, lifetime and after 5000 occurrences. They can be specified in any order and need to be separated by commas (only if there are multiple options to an action, the first option must not be preceded by comma).
So far I spoke about 10046 event which is used for tracing, but there are other uses for diagnostic events.
Every ORA- error code in Oracle checks for an event with the same number. In fact Oracle diagnostic events and ORA- errors share the same range of numbers from 0 to 65535 for their codes (you can see most of them in $ORACLE_HOME/rdbms/mesg/oraus.msg file)
So, for example ORA-60 which is “deadlock detected” error will also check for event number 60 and if it is set, it will invoke its action(s) before sending the deadlock exception up the application stack.
For example, I could invoke hanganalyze at level 4 when ORA-60 is hit in my session:
SQL> alter session set events '60 trace name hanganalyze level 4';
Previous Next
.
