Retention Policy for ADR

郑全

Retention Policy for ADR (Doc ID 564269.1)        To BottomTo Bottom       

In this Document
Purpose
Scope
Details
References
APPLIES TO:
Oracle Database - Enterprise Edition - Version 11.1.0.6 and later
Oracle Database - Standard Edition - Version 11.1.0.6 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
*** Checked for relevance on 13-Mar-2013 ***
PURPOSE
The goal of this document is to explain the retention policies in Automatic Diagnostic Repository (ADR).

SCOPE
All DBAs working on 11g databases.

DETAILS
There are two time attributes which are used to manage the retention of information in ADR.
Both attributes correspond to a number of hours after which the MMON (Memory Monitor) background process removes the expired ADR data:


- SHORTP_POLICY :  used to purge information that have a short life.
Default is 720 which corresponds to 30 days - approximately 1 month.

- LONGP_POLICY: to purge ADR contents that have a long life.
Default is 8760 = 365 days = 1 year.

To view and modify these settings, you can either use the Enterprise Manager 11g DB Control GUI or via the ADR Command Interpreter (ADRCI) started from an O/S prompt.

In this note, we will detail you how to check and change the above parameters via ADRCI.

As some of the ADRCI commands (like "show control") do not work with multiple current ADR homes, we need to first select the appropriate homepath:
% adrci

adrci> show home
ADR Homes:
diag/rdbms/<SID>/<SID>
...

adrci> set home <ADR HOME PATH>


To check the current values of SHORTP_POLICY and LONGP_POLICY :
adrci> show control

To set the retention policy values :
adrci> set control (SHORTP_POLICY = 3600)

To get help on the set control command :
adrci> help set control

All ADRCI commands are described in the "Oracle Database Utilities 11g Release 1 (11.1)" Documentation Part Number B28319-02 - accessible online:
http://download.oracle.com/docs/ ... 11/b28319/adrci.htm

A few more comments worth to mention:
- Up to 11.1.0.7, CDUMP files were not purged due to unpublished Bug 6343743.

- Incidents in a "Tracking" state are indefinitely kept in ADR.
To determine the status of an incident :

adrci> show incident -mode detail - p "incident_id=..."