OERR - Secrets of the Oracle Database - page 462

Running this shell script against Oracle9 i yields 623 events, while Oracle10 g has 713 events.
Oracle11 g has 761 events. Following is a small excerpt of the output generated by the script
oerr.sh , which contains some of the better known events such as 10046 and 10053.
10046, 00000, "enable SQL statement timing"
// *Cause:
// *Action:
10047, 00000, "trace switching of sessions"
// *Cause:
// *Action:
10048, 00000, "Undo segment shrink"
// *Cause:
// *Action:
10049, 00000, "protect library cache memory heaps"
// *Cause:
// *Action: Use the OS memory protection (if available) to protect library
// cache memory heaps that are pinned.
10050, 00000, "sniper trace"
// *Cause:
// *Action:
10051, 00000, "trace OPI calls"
// *Cause:
// *Action:
10052, 00000, "don't clean up obj$"
// *Cause:
// *Action:
10053, 00000, "CBO Enable optimizer trace"
// *Cause:
// *Action:
10056, 00000, "dump analyze stats (kdg)"
// *Cause:
// *Action:
10057, 00000, "suppress file names in error messages"
// *Cause:
// *Action:
Instead of oerr on UNIX, you can use the following anonymous PL/SQL block on any platform
where an ORACLE client is available (file oerr.sql ):
SET SERVEROUTPUT ON SIZE 1000000
DECLARE
err_msg VARCHAR2(4000);
counter number:=0;
BEGIN
FOR err_num IN 10000..10999
LOOP
err_msg := SQLERRM (-err_num);