Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: 10053 trace for sql fired from pl/sql (stored code)

RE: 10053 trace for sql fired from pl/sql (stored code)

From: Luis Fernando Cerri <lcerri_at_santanderbanespa.com.br>
Date: 2005-12-23 00:09:26
Message-id: A70750EC2FDE6A4C98FCA68CC6AC283302C0767D@bsbrsp42.bs.br.bsch


As Wolfgang states in his brilliant document, "the query must be (hard) parsed and it must be parsed by the CBO". Maybe the original poster is missing these requirements.  

Best regards,
Cerri         

-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Radoulov, Dimitre
Sent: quinta-feira, 22 de dezembro de 2005 18:52 To: oracle-l_at_freelists.org
Cc: Boris Dali
Subject: Re: 10053 trace for sql fired from pl/sql (stored code)

> 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    

Essa mensagem é destinada exclusivamente ao seu destinatário e pode conter informações confidenciais, protegidas por sigilo profissional ou cuja divulgação seja proibida por lei. O uso não autorizado de tais informações é proibido e está sujeito às penalidades cabíveis.

This message is intended exclusively for its addressee and may contain information that is confidential and protected by a professional privilege or whose disclosure is prohibited by law. Unauthorized use of such information is prohibited and subject to applicable penalties. Received on Fri Dec 23 2005 - 00:09:26 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US