Re: 10053 trace for sql fired from pl/sql (stored code)
- From: "Radoulov, Dimitre" <cichomitiko@xxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 22 Dec 2005 22:52:25 +0100
> It works with 9i.
I tested it on 9.2.0.4 and 9.2.0.7 on Solaris. The execute immediate 'alter
session set events ''10053 trace name context forever, level 1''' within a
plsql block doesn't seem to provide the expected information. The same code
works with event 10046.
You could try to trace with 10046 to get the sql and the values of the bind
variables and then trace with 10053 in sqlplus, but in this way you could miss
an important session environment information (if the application sets some
parameters before calling the plsql code for example).
So you can create a logon trigger that executes "alter session set events
'10046 ... " for that particular user to see the entire application code.
Regards,
Dimitre Radoulov
Other related posts:
