To: mgogala@xxxxxxxxxxx, oracle-l <oracle-l@xxxxxxxxxxxxx>
Date: Sat, 30 Sep 2006 22:57:11 -0700 (PDT)
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.
HTH,
Deepak
--- Mladen Gogala <mgogala@xxxxxxxxxxx> wrote:
> I've had an overly active batch process (J0001) but
> I was unable to
> see the SQL. The address in V$SESSION was empty.
> After that, I tried
> with SMON. No luck, there, either. Essentially, in
> version 10.2.0.2 SQL
> statements executed by the background processes are
> not visible:
>
> SQL> select
> sql_address,sql_id,prev_sql_addr,prev_sql_id,
> program
> 2 from v$session where sid in (69,70,75)
> 3 /
>
> SQL_ADDR SQL_ID PREV_SQL PREV_SQL_ID
> PROGRAM
> -------- ------------- -------- -------------
> --------------------
> 00 00
> oracle@xxxxxxxxxxxxx
>
> (SMON)
>
> 00 00
> oracle@xxxxxxxxxxxxx
>
> (CKPT)
>
> 00 00
> oracle@xxxxxxxxxxxxx
>
> (PMON)
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
http://www.freelists.org/webpage/oracle-l
