Nothing exciting today, just some things to remember:
DBMS_SCHEDULER tracing is done via the event 27402, like
alter system set events '27402 trace name context forever, level 65355';
This gives several interesting traces
- trace of the job scheduler itself, in *cjq*.trc files
- trace of the session creation/running the jobs, in *ora*.trc files
- trace of the job slaves – in *j0*.trc files
Some things to remember:
- the event needs to be set at system level, it does not appear to do anything at session level
- in multitenant, you need to set it at ROOT level, at least to get the cjq traces
- in RAC – remember to set it at all instances if required
One thought on “Tracing DBMS_SCHEDULER”