Previous Topic: Example 2 Pre-Flight Check: CHECK Failed

Next Topic: Group History Cleanup Operations

Post-Upgrade Cleanup Operations

Only required if upgrading from version 5.0.

If you upgraded your CMS from version 5.0, you must check the following ‘cleanup’ database tables. Entries in these tables indicate that database violations were found and fixed during the upgrade.

DB table

Contains details of

WGNDUPUG1

Type 1 cleanups, user group history

WGNDUPUG2

Type 2 cleanups, user group history

WGNDUPUG3

Type 1 cleanups, audit state

WGNDUPUG4

Type 2 cleanups, audit state

When you upgrade a CMS, cleanup operations check for database violations in the user and audit tables. If necessary, the cleanup operations delete offending entries from these tables. But before deleting any data, the cleanup operation writes details of the violations to the tables listed above.

Entries in WGNDUPUG1 or WGNDUPUG3 tables after upgrading

This indicates a Type 1 cleanup was required. These table entries indicate that any violations were successfully fixed and no further action is required.

Be aware that the cleanup operation may potentially affect subsequent event searches or reports. This may happen if, as a result of the data cleanup, a user moves in or out of a reviewer’s management group (see the following ‘group history cleanup’ section for details).

Entries in WGNDUPUG2 or WGNDUPUG4 tables after upgrading

This indicates a Type 2 cleanup was required. Manual intervention may be needed to restore corrupt data. Please contact CA Technical Support.