Re: Powerful OCI debugging technique, but how??

try:
"alter session set sql_trace=true"

After it gets set back to false or your session terminates, a trace file will be created on the server side which can be viewed or further processed with tkprof.

-Peter

Ramon F Herrera wrote:
>
> I have been doing some OCI programming lately, from
> a Linux client to a SPARC server; obviously, I have been
> using the debugger (gdb) a lot. It occurred to me that
> all the debugging info I have is from the client side
> only, but there must be some way to do server-side
> debugging. Is there a method to place the Oracle
> server in "monitoring" or "debugging" mode? I wouldn't
> mind setting up an Oracle server for my exclusive use,
> and to have it log any request (IF there is a request
> at all!) received over the network, or even locally.
>
> Sometimes my OCI programs run fine, up the the
> "OCIStmtExecute" function which may execute without errors,
> but not give the expected result, or it may even fail with
> a vague error message. In this cases the programmer
> needs to know exactly what SQL statement was received
> by the server.
>
> How can we do that?
>
> TIA,
>
> -Ramon F. Herrera
Received on Wed Jun 05 2002 - 15:24:10 CDT