RE: dba_hist_sql_plan

  • From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
  • To: "Chris.Stephens@xxxxxxx" <Chris.Stephens@xxxxxxx>, "JBECKSTROM@xxxxxxxxx" <JBECKSTROM@xxxxxxxxx>, oracle-l-freelists <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 2 Jun 2010 10:17:26 -0700

I'm not positive about this, but I think with the way ASH captures activity the 
AWR snapshots may not have that same problem of cursors aging out of the pool 
between snapshots like we see all the time with Statspack.  I've never tested 
it out myself, but I seem to remember seeing someone else state this same thing 
on this list a few months back and it sounds reasonable to me.

From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Stephens, Chris

Also, it's entirely possible that your sql was pushed out of the shared pool by 
the time the snapshot was taken.

Privileged/Confidential Information may be contained in this message or 
attachments hereto. Please advise immediately if you or your employer do not 
consent to Internet email for messages of this kind. Opinions, conclusions and 
other information in this message that do not relate to the official business 
of this company shall be understood as neither given nor endorsed by it.

Other related posts: