In article <1188388608.487786.253110_at_w3g2000hsg.googlegroups.com>,
johnbhurley_at_sbcglobal.net says...
> Hacking up some triggers and putting some low level traces on is
> another way since you are just testing.
>
>
No need for triggers. DBMS_SCHEDULER.RUN_JOB has two arguments: job name
and "run in current session". Simply, set up 10046 trace, level 12 and
run the job with the second argument set to TRUE. Of course, nothing
will show up, as the package text is encrypted, so the arguments to the
DBMS_STATS will not be visible.
Received on Wed Aug 29 2007 - 10:01:44 CDT
