Upgrade Guide › Upgrading Databases › Post-Upgrade Cleanup Operations › Audit State Cleanup Operations

Audit State Cleanup Operations

This problem parallels the user group database violations described in the previous section. When a reviewer audits an event in a CA DLP console, the relevant audit issue gets updated and the state of the audit type changes to a new value. For example, the audit type ‘Status’ may change its state from ‘Deferred’ to ‘Not approved’. But rare instances have been identified where an audit type is simultaneously set to multiple states. This was fixed in version 6.0.

Now in CA DLP, the ‘single state’ constraint on audit types is enforced in the CMS database. Consequently, when you upgrade your CMS, a database cleanup operation eliminates any schema violations.

Such violations are rare and the cleanup operation will not normally need to take any action. But if it does detect event issues with a corrupt audit history, it takes the following steps:

Type 1 Cleanup

Where possible, the cleanup operation simply retains the newest state of any affected audit type (the state most recently specified by a reviewer) and deletes any other current states. The remaining history for that audit type (all its previous states) are retained if their integrity is otherwise intact; if the remaining history is also corrupt, a Type 2 cleanup is needed.

Before the cleanup operation deletes any invalid current states from the issue’s audit trail, it saves these details to the WGNDUPUG3 database table. After any CMS upgrade, you need to check for entries in this table.

Note: This ‘simple’ form of audit type corruption is the only form we have observed in the field.

Type 2 Cleanup

If the audit trail for the affected audit type contains too many errors and the database violations prove intractable, the cleanup deletes the entire history for the affected audit type, retaining only its most recent current state.

Before the cleanup operation deletes any invalid states, it saves these details to the WGNDUPUG4 database table. After any CMS upgrade, you need to check for entries in this table.

Note: Such complex examples of audit type corruption have never been observed in the field.