Re: Help me, please - Problems with Oracle Trace

You can set events in other sessions with the oradebug feature of Server Manager. Use the following commands to set the event in the already-running session:

oradebug setorapid <pid>
oradebug event 10046 trace name context forever, level 4

Note: the pid is the Oracle pid from v$process, not the O/S pid. The trace output will write to the user_dump_dest.

--
Jeremiah Wilton http://www.wolfenet.com/~jeremiah

On Sun, 15 Nov 1998, FireHawk wrote:
>
> But the problem is: I can't access source code to put an alter session
> comand. Is there a same "alter system" to put in init*.ora ? Thanks a
> lot
>
> Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk> wrote:
> >
> >Alter session set events '10046 trace name context forever, level 4'
> >causes trace to dump all values of bind variables.
> >
> >
> >FireHawk <dba_at_freemail.com.br> wrote:
> >>
> >> When I make a Oracle trace (alter session set sql_trace=true) the
> >> output is
> >> any as:
> >> SELECT CORP,HOUSE,CUST,EQP_TABLE_CODE
> >> FROM CUST_OUTLET
> >> WHERE HOUSE=NVL(:b1,' ')AND CUST=
> >> NVL(:b2,' ')
> >> But, I don't need the b1 and b2 parameters.
> >> I need the contents of b1 and b2.
Received on Sun Nov 15 1998 - 09:20:44 CST