How to purge off some old audit results from the Guardium appliance

The database is full. Old audit results need purging from the Guardium Appliance.


The database is full.


Normal purging of audit results is set in the audit process definition by the Keep for a minimum of x days or y runs option. Normal purging of audit results does not occur if the items in the Audit Process To-Do List were not handled or signed off. For example, if the To-Do List has items from 6 months ago, then no audit results since 6 months ago are purged.

Resolving the problem

Users must handle their To-Do Lists in a timely fashion, so the purging happens and the database does not fill up. Adding a Receiver is not mandatory when you create a new Audit Process. An Audit Process without a receiver can be used when results of the Audit Process are sent to the third-party application, and the Audit Process results do not need to be viewed or signed. If you still want to add a receiver but not require viewing or signing the Audit Process results, clear the To-Do List checkbox, but set the Email format field to Full Results (PDF or CSV). In this scenario, the status gets set to VIEWED and the receiver does not have to view the results to make them eligible for purge. If the To-Do List checkbox is cleared but the Email format field is set to None or Links only, the To-Do entry is created for the receiver because:
  • These types of notifications do not set the status to VIEWED.
  • The results cannot be purged.
The internal Guardium table REPORT_RESULT_DATA_ROW often gets large if the audit jobs or To-Do Lists are not handled or signed off.
Manual purge command
This command is a way to manually purge audit results. Use it only if the normal audit results purge is not working. It is recommended to contact Technical Support to understand why normal purge is not working. Use this command only when absolutely necessary to deal with audit tasks that produce a high number of records and take up too much disk space. Consult with Technical Support before you run this command. The response includes a warning message and a confirmation step.
  • support clean DAM_data audit_results <start_date> <end_date>
  • support clean DAM_data audit_results <end_date>