Upgrade Guide › Upgrading Databases › Upgrading a Partitioned Oracle Database › Semi-automated Database Upgrades

Semi-automated Database Upgrades

If your database partitioning scheme follows the CA DLP default configuration (in terms of naming conventions, the MAXVALUE partition, tablespace, and so on), you can upgrade your Oracle CMS from r12.0 by running the CA DLP installation wizard, setup.exe, and then manually running a stored procedure after the wizard completes.

During these upgrades, if the installation wizard detects a partitioned database, it makes the following changes:

• New partitioned table: Wgn3IssueTrigger

  By default, the installer creates this table in the same tablespace as the Wgn3IssueParticipant table.

  This table is named Wgn3IssueTrigger with a single MAXVALUE partition.

  After upgrading the CMS, you need to manually run a stored procedure. This automatically adds further partitions to Wgn3IssueTrigger to match the names, size and number of partitions used by other tables in your CMS database.

• New index: Wgn3Trigger.PolicyID

  By default, the installer creates a new index on the PolicyID column in the Wgn3Trigger table. In a partitioned database, it creates a local index in the same tablespace as the index on Wgn3Trigger.TriggerName.

For full upgrade instructions and for details about the post-upgrade stored procedure, see the references below.

More information:

Table Partitioning SP