Dimitre and all,
> It works with 9i.
I tested it on 184.108.40.206 and 220.127.116.11 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.
Wolfgang Breitling Centrex Consulting Corporation www.centrexcc.com -- http://www.freelists.org/webpage/oracle-l