Health alerts and UI banner warning: Old partitions found

Symptoms

The condition is marked by the following symptoms:
  • The Deployment Health Dashboard on a central manager shows events with the name Old Partitions Found. The events may come from one or many managed units or from the central manager itself.
  • After logging into the Guardium UI, a UI banner warning shows Old partitions found: Oldest partition found: p[date].

Causes

The symptoms appear when old partitions exist on the internal system database. The severity of the alert corresponds to the age of the partitions, and the default values are as follows:
  • Medium severity: partitions older than the purge age plus 62 days
    • A UI banner warning shows on all systems with a medium severity alert
  • High severity: partitions older than the purge age plus 120 days
  • Critical severity: partitions older than the purge age plus 240 days
The purge period of the system is shown on the Data Archive page of the Guardium UI, and the date of the oldest partition is shown in the details section in the format YYYYMMDD.
Note: The purge period is based on the ADDITIONAL_PURGE_AGE parameter. The default value is 60 days. Do not change this value without consulting Guardium support.
There are several possible root causes for having old partitions on the system, for example:
  • Days have not been archived or exported and therefore have not been purged
  • Invalid timestamps are causing data to not be purged
  • There are corrupted partitions that cannot be dropped by the purge process

Environment

The condition may apply to Guardium collectors, aggregators, and central managers.

Resolving the problem

Resolve the problem using the following guidance:
  1. Resolve any existing Data not exported or archived: [n] days have not been exported or archived and do not meet the purge criteria UI banner warnings. These warnings will appear on units where days have not been exported or archived. For more information, see UI banner warning: Data not exported or archived
  2. Upgrade to latest patch bundle. Known cases where purge could not clear partitions may be resolved in latest version.
  3. If problem remains, resolution may depend on several factors:
    • How much data is on the Guardium system
    • How many old partitions exist
    • The root cause explaining the old partitions
    • Whether you have previously attempted to clean up the old partitions
    • How many Guardium systems are affected
    Contact Guardium support to begin resolving this issue. Provide the following must gather information:
    • support must_gather patch_install_issues
    • support must_gather agg_issues
    • support must_gather system_db_info
Note: The following document contains an internal section that Guardium support can consult to resolve the problem: IBM Security Guardium v10.0p9998 health check errors - Data older than purge period or Old partitions found.