This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

DPA Repository Database Size Growing

FormerMember
FormerMember

Hi all,

We have been using DPA since this year March, and we realized the repository database size has been growing.

Based on the guidebook that we have followed, it was said that for a high activity database instance, the disk space required is 5GB.

We are monitoring about 6 instances, and so far we have been allocating about 200GB space for it.

Is there any purging job being setup for this repository database?

Parents
  • There is a purging job called the cleaner service that runs nightly. This removes data in the detail tables that is older then the CLEAN_DAYS_OF_DETAIL setting that gcp​ mentioned.

    The table CONDPRM should have a LR_CLEAN date for each monitored instance. Do open a case and send the logs to support.

Reply
  • There is a purging job called the cleaner service that runs nightly. This removes data in the detail tables that is older then the CLEAN_DAYS_OF_DETAIL setting that gcp​ mentioned.

    The table CONDPRM should have a LR_CLEAN date for each monitored instance. Do open a case and send the logs to support.

Children
No Data