Grid Control Repository: How to Modify the Retention and Purging Policies for Metric Data?

(Doc ID 430830.1)

Last updated on DECEMBER 01, 2016

Applies to:

Enterprise Manager Base Platform - Version 10.2.0.2 to 11.1.0.1 [Release 10.2 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on 26-08-2012***
Checked for relevance on 27-Jan-2014

Goal

The metric data that is collected and uploaded by the Agents on the targets hosts is called the 'raw' data, which is stored by the OMS into the repository tables. One of the DBMS_Job's (Rollup job) in the Repository is reponsible for rolling up / aggregating this raw data into 1Hour metric tables, which are further rolled up into 1Day tables. The 1Hour and 1Day is used for providing historical metric information in the Grid Console UI pages. The 3 tables that store this data are:

MGMT_METRICS_RAW
MGMT_METRICS_1HOUR
MGMT_METRICS_1DAY

After the data is aggregated, it considered eligible for purging. However, a certain period of time has to pass for data to actually be purged. This period of time is called the Retention time.
The goal of this document is to provide information on how to modify the Grid Control Default Retention and Purging Policies in 10g Grid Control.

Note:

The default aggregation and purging policies have been designed to provide the most available data for analysis while still providing the best performance and disk-space requirements for the Management Repository. As a result, these should not be modified to improve performance or increase the available disk space. Increasing the retention time drastically can affect the performance of the Management Repository and have adverse reactions on the scalability of the Enterprise Manager installation.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms