On 10/01/2006 01:57:11 AM, Deepak Sharma wrote:
> We noticed that too and with the job queue process
> it's a real pain. There are 2 workarounds I've tried,
> but also want to know if there's any better option:
>
> (1) Use PLSQL_OBJECT_ID from v$session, if that job
> happens to be a PL/SQL.
>
> or
>
> (2) Use dba_jobs_running and v$open_cursor for the SID
> being traced.
I enabled 10046 for the process, but that is not as convenient and
efficient as using some nice gooey monitor tool. I will open a TAR
(SR) and get Oracle to tell me whether this is a bug to be fixed or
a feature.
--
Mladen Gogala
http://www.mladen-gogala.com
--
http://www.freelists.org/webpage/oracle-l
Received on Sun Oct 01 2006 - 09:50:33 CDT
