Upgrade Guide › Upgrading Databases

Upgrading Databases

This chapter describes the database issues associated with upgrading your CMS. Note the following issues if upgrading from version 5.0 or 6.0:

CMS upgrades from 5.0 or 6.0 require database schema change

In r12.0, some schema changes were made to the Wgn3EventParticipant database table to accommodate changes to security model handling.

Consequently, if upgrading from versions that predate r12.0, you must run a ‘pre-flight check’ before upgrading your CMS to estimate how long the database changes will take.

After upgrading your CMS, you also need to make a manual change to the Wgn3EventParticipant table.

CMS upgrades from 5.0 may require cleanup operations

If upgrading your CMS from version 5.0, cleanup operations check for database violations in the user and audit tables. If necessary, the cleanup operations delete offending entries from these tables but in rare cases, you may need to manually restore corrupt data.

This section contains the following topics:

Database Schema Changes

Pre-upgrade Database Considerations

Upgrading a Partitioned Oracle Database

Database Upgrade Procedure

Post-Upgrade Cleanup Operations