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

  • From: Wolfgang Breitling <breitliw@xxxxxxxxxxxxx>
  • To: Christian.Antognini@xxxxxxxxxxxx
  • Date: Fri, 23 Dec 2005 11:37:55 -0700

Boris, Christian,

that is an excellent comment. I recall that when doing tests in a sqlplus session, I need to execute some other sql afterwards - even though the original sql HAS finished - for the statistics to show up (viewing from a second session, else the sql to query v$sql_plan_statistics already IS another sql). I believe sqlplus keeps the cursor of the most recent sql statement open, so it may be that the cursor needs to be closed for the statistics to be "populated". But then these are v$ views, so there is nothing to BE populated.

Christian Antognini wrote: 
Boris


3) Another stupid question, just taking advantage of
you being here - do you know when EXACTLY
v$sql_plan_statistics gets populated? Sometimes I get
a result set back sometime ago, and the plan is
visible in v$sql_plan,  but the stats are still all
zeros in v$sql_plan_statistics.


One possibility is that the SQL statement is still running. In fact the execution stats are available only when the execution is over. 



--
Regards

Wolfgang Breitling
Centrex Consulting Corporation
www.centrexcc.com
--
//www.freelists.org/webpage/oracle-l


Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 12-2005