Re: Any way to look at SQL statements sent to database?

Randi -

I don't have any opinion on the ocispy tool that Herman is recommending, but is there anything wrong with a plain ol' trace on your particular session? If you're not familiar with it, check out the session-modifiable parameter SQL_TRACE. When turned on, a trace file will be created for each session to which SQL_TRACE applies. To make the trace file (you can find it under whatever directory is specified in user_dump_dest) more readable, run it through tkprof and its sorting options in order to make the tkprof output appear in whatever order (elapsed CPU time, number of buffer gets, e.g.) you like.

I don't know of a way to obtain the values of bind variables using this technique,
but it works pretty well. I use it all the time to find out what my third-party application is doing behind the scenes.

Happy trails,
Tom

Herman de Boer wrote:

> Randi Wølner wrote:
>
> >
> >Long time ago I saw a tool that could show all SQLs sent from the current PC
> >to a Oracle database server. This tool could be used as a "spy" if one did
> >not have access to the source code, but would like to know what query was
> >executed (for example if someone gave you MS Access .MDE file with reports
> >where you are not able to read the query).
> >
> >If anyone know what product this might have been (or any similar) please let
> >me know.
> >
> >Thank you!
> >
> >Best regards
> >Randi Wølner
> >
> >
>
> See http://www.geocities.com/ocispy/
>
> Kind Regards,
>
> Herman de Boer
> sr consultant
> IT Consultancy Group bv
Received on Mon Aug 05 2002 - 14:36:59 CDT