Re: Stalling stored procs?

You could use svrmgrl

connect internal <g>
oradebug setospid YOURSPID
oradebug unlimit
event 10046 trace name context forever, level 12

The <g> is a grin becaus I know all about connect internal going away - and YOURSPID is the spid for the process you want to trace - the trace will wind up in $UDUMP - as an ora_spid_SID.trc -

If you want to turn off tracing, then you can do the above, except the last line would be:

event 10046 trace name context off

Of course this is all easier if you have a script, But it still doesn't require you to bounce your database - which would be a big deal for me too :)

On Mon, 16 Oct 2000 20:44:21 GMT, Greg Weston <gwestonREMOVE_at_CAPShome.com> wrote:

>In article <9frkussr7abgv25qga7rtf5g7sfac9qge2_at_4ax.com>, Kirt Thomas
><kremovethisspamthingthomas_at_gfsiinc.com> wrote:
>
>> Also - can't you turn on tracing?
>
>I'll try the queries you suggested (after checking the alert log...I
>really must be tired to have not looked there already). As for turning
>on tracing...still requires a DB shutdown, right? The industry I'm in
>is psychotic enough to have a bigger problem with downtime - even a
>couple of minutes - than with sporadic timeouts.
>
>G
Received on Mon Oct 16 2000 - 20:54:49 CDT