The Guardium internal database is filling up
Symptoms
The Guardium internal database is filling up and most of the data is in the GDM_POLICY_VIOLATIONS_LOG table.
Causes
A change to the policy can cause a policy violation rule to be triggered frequently. You might find that most of the data is stored in the GDM_POLICY_VIOLATIONS_LOG table.
Environment
The Guardium collector is affected.
Diagnosing the problem
Run the CLI command support show db-top-tables all.
Resolving the problem
Check the Policy Violations / Incident Management report to identify which policy rule is getting triggered constantly. Then, adjust the policy rule to prevent it from getting triggered as often.
The excess data in the GDM_POLICY_VIOLATIONS_LOG table is purged as part of the regular purge strategy. However, if you would like to manually clean data from GDM_POLICY_VIOLATIONS_LOG table, you can use the command support clean DAM_data policy_violations<start_date><end_date>.