I did run the 10046 trace, and the trace file only contained all of the
waits, as shown above.
Steve Howard wrote:
> buccellik wrote:
> > We were given an executable problem, from ESRI, to fix duplicate data
> > in our database. The executable runs forever, we have never gotten it
> > to finish, but killed it. When I do a trace on the database session it
> > produces, the trace file is nothing but the following:
> > WAIT #7: nam='SQL*Net message to client' ela= 3 p1=1111838976 p2=1 p3=0
> > WAIT #7: nam='SQL*Net message from client' ela= 66 p1=1111838976 p2=1
> > p3=0
> > WAIT #7: nam='SQL*Net break/reset to client' ela= 3 p1=1111838976 p2=1
> > p3=0
> > WAIT #7: nam='SQL*Net break/reset to client' ela= 63 p1=1111838976 p2=0
> > p3=0
> > WAIT #7: nam='SQL*Net message to client' ela= 3 p1=1111838976 p2=1 p3=0
> >
> > When I use Performance Overview, I can see an SQL statement associated
> > with the session. However, I would like to run that statement on my
> > own, but I don't know what values are in the bind variables. Does
> > anyone know how I can find out the values for the bind variables?
> >
> > Thanks.
>
> Hi,
>
> Version? (the answer varies)
>
> You should be able to run a 10046 trace to get the values. Look for it
> on metalink, or google for it.
>
> Regards,
>
> Steve
Received on Fri Jul 07 2006 - 08:45:31 CDT
