RE: SPM again
- From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- To: "john.kanagaraj@xxxxxxxxx" <john.kanagaraj@xxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 11 Mar 2010 15:59:55 -0700
Why not just create a few preserved snapshots at your desired interval to
retain older plans in AWR?
For more info:
http://download.oracle.com/docs/cd/B19306_01/server.102/b28051/tdppt_degrade.htm#CIHDHEAA
You can do the same thing in statspack too - from 10g
$ORACLE_HOME/rdbms/admin/spdoc.txt:
8.1. Baselining performance data
It is possible to identify snapshot data worthy of keeping, which will not
be purged by the Statspack purge. This is called baselining. Once you have
determined which snap Ids or times of day most represent a particular
workload whose performance data you would like to keep, you can mark the
data representing those times as baselines. Baselined snapshots will not
be purged by the Statspack purge.
Regards,
Brandon
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of John Kanagaraj
I would like to turn on OPTIMIZER_CAPTURE_SQL_PLAN_BASELINES in
the Dev/Test/Stage environments, capture Plans and use SPM to store
this longer term without the overhead of either creating my own custom
copy of AWR or (worse!) retaining AWR for substantially longer
periods.
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.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
