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

Semi-automated Database Upgrades

(Applies to upgrades from 12.0 or later)

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

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.

New partitioned table: Wgn3RelatedEvent

By default, the installer creates this table in the Default tablespace unless the customization specifies a different location.

This table is named Wgn3RelatedEvent with a single MAXVALUE partition.

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

To perform a semi-automated upgrade

1. Run setup.exe on the server hosting the CMS.

   Find this file in the root of the CA DataMinder distribution image.

   CA DataMinder automatically detects that you are upgrading and launches the server installation wizard.

2. Follow the on-screen instructions. Continue to the final wizard screen and click Install.
3. Run a stored procedure to modify the newly-created database table, Wgn3IssueTrigger, so that it matches the other partitioned tables in your database in terms of size, number and names of partitions.

   This stored procedure was installed when you upgraded your CMS. It is called:

   WGN_PARTITION_UTIL.WGN_PARTITION_12_5_TABLES
   

4. Run the following command to modify the newly-created database table Wgn3RelatedEvent, so that it matches the other partitioned tables in your database in terms of size, number, and names of partitions.

   SQL> EXEC Wgn_Partition_Util.wgn_partition_new_table(
          new_table_name  => 'WGN3RELATEDEVENT',
          template_name   => 'WGN3EVENT',
          pdebug          => True,
          db_type         => Wgn_Partition_Util.wgn_db_type_CMS,
          Tablespace_Name =>
          Wgn_Partition_Util.wgn_get_tablespace_name('WGN3RELATEDEVENT')
        );