Upgrade Guide › Upgrading Databases › Upgrading a Partitioned Oracle Database › Native Script Upgrades from r12.0

Native Script Upgrades from r12.0

These instructions upgrade your CA DataMinder database from 12.0 to 12.5.

If your database partitioning scheme follows the CA DataMinder default configuration, you can use the semi-automated upgrade method. If you require more control and flexibility in managing your Oracle database, use the Native Upgrade scripts to upgrade. In both cases, you must run a stored procedure after upgrading your CMS.

To run a semi-automated upgrade

1. Upgrade the CMS by running setup.exe.

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

   The CA DataMinder database is upgraded accordingly, and includes the changes described in the section, 'Semi-automated Database Upgrades'.

2. Run the following command as the schema owner, using the SQL*Plus utility:

   EXEC WGN_PARTITION_UTIL.WGN_PARTITION_12_5_TABLES;
   

   Applying this stored procedure ensures that the Wgn3IssueTrigger table matches your existing partitioning scheme.

To upgrade using the native upgrade scripts

1. Go to the \UpgradeV12_0ToV12_5 subfolder in your CA DataMinder distribution image.
2. Copy this subfolder to your database host server.

   This subfolder includes Native_UpgradeToVer3_60.sql and Native_Wrapper.sql.

3. Edit Native_UpgradeToVer3_60.sql on your database host server to make the changes you require.

   In particular, you may want to specify the tablespace and storage parameters for these new objects:

   Captured Data Index

   IX_Wgn3Trigger_PolicyID

   Note: By default for new CA DataMinder installations, this index is assigned to the WGNDATAIDX tablespace.

   Audit Data Table

   Wgn3IssueTrigger

   Note: By default for new CA DataMinder installations, this table is assigned to the WGNDATA tablespace.

   Audit Data Indexes

   PK_Wgn3IssueTrigger

   IX_Wgn3IssueTrigger_Trigger

   Note: By default for new CA DataMinder installations, these indexes are assigned to the WGNDATAIDX tablespace.

   Other Tables

   Wgn3Role

   Wgn3ResourceType

   Wgn3Resource

   Wgn3ResourceRole

   Wgn3UserRole

   Note: By default for new CA DataMinder installations, these tables are assigned to the WGN tablespace.

   Other Indexes

   IX_Wgn3UserDateGroup

   IX_WGN3GroupUpdateUser

   PK_Wgn3Role

   UK_Wgn3Role_Name

   IX_Wgn3Role_Parent

   PK_Wgn3ResourceType

   UK_Wgn3ResourceType_Class

   PK_Wgn3ResourceIX_Wgn3Resource_Policy

   IX_Wgn3Resource_ResourceType

   PK_Wgn3ResourceRole

   IX_Wgn3ResourceRole_Resource

   PK_Wgn3UserRole

   IX_Wgn3UserRole_User

   Note: By default for new CA DataMinder installations, these indexes are assigned to the WGNIDX tablespace.

4. Run the following command as the schema owner, using the SQL*Plus utility:

   SQL> set serveroutput on size unlimited
   SQL> start Native_Wrapper.sql;
   

   Important! Always use a version of SQL*Plus that matches your version of Oracle. Errors can occur if you use an older version of SQL*Plus to run scripts against a newer version of Oracle.

5. Upgrade the CMS by running setup.exe.

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

   The CA DataMinder database is upgraded accordingly, and includes the changes described in the section, 'Semi-automated Database Upgrades'.

6. Run the following command as the schema owner, using the SQL*Plus utility:

   EXEC WGN_PARTITION_UTIL.WGN_PARTITION_12_5_TABLES;
   

   Applying this stored procedure ensures that the Wgn3IssueTrigger table matches your existing partitioning scheme.

7. You now need to upgrade from r12.5; see the next section.

More information:

Semi-automated Database Upgrades

Table Partitioning SP