Description:
CA DLP provides Native Upgrade scripts for customers who require flexibility in managing the database for their Oracle CMS. For example, these scripts enable DBAs to use their own tablespace and partition naming conventions. You can find these scripts in the CA DLP distribution image, in the \Support\NativeSchemaSQL\ORACLE\Partitioned folder.
The "UpgradeV5_0ToV6_0" script in this folder is required if you are upgrading a 5.0 CMS where the database is partitioned and/or you need to customize physical attributes of objects in the upgrade. These scripts comprise the first stage in the pre-upgrade process.
The "UpgradeV6_0ToV12_0" script in this folder is needed if you are upgrading a partitioned 5.0 or 6.0 CMS where the database is partitioned and/or you need to customize physical attributes of objects in the upgrade. If upgrading from 5.0, these scripts comprise the second stage in the pre-upgrade process.
The "UpgradeV12_0ToV12_5" script in this folder is needed if you are upgrading a partitioned r12.0 CMS where the database is partitioned and/or you need to customize physical attributes of objects in the upgrade. If upgrading from 5.0 or 6.0, these scripts comprise the third or second stage respectively in the pre-upgrade process.
For more details please refer to the upgrade documentation on the CA DLP Documentation Pages of the CA Support Online (support.ca.com).
If the upgrade from 6.0 to 12.0 was executed using the "UpgradeV6_0ToV12_0" Native script, when attempting to upgrade to CA DLP r12.5 you may encounter the following error:
A Java runtime error occurred. (code 0xe5630088).
Description: 'java.lang.Exception: wigan.infrastruct.WgnException: SQL exception at line 88 of 'WGN_V_JOB.sql' : 955: [CA DLP][Oracle JDBC Driver] [Oracle]ORA-00955: name is already used by an existing object containing java.sql.SQLSyntaxErrorException: [CA DLP][Oracle JDBC Driver][Oracle]ORA-00955: name is already used by an existing object'.
This error occurs because the 12.0 and 12.5 install attempts to create a synonym called WGN3STATSSTATE. Prior to CA DLP r12.0 WGN3STATSSTATE was a table name, so if any attempt to create a synonym of the same name will fail if the table still exists.
Unfortunately if the DB was upgraded from 6.0 To 12.0 via the "UpgradeV6_0ToV12_0" Native script the "wgn_stats" package is not updated. This package automatically creates the table WGN3STATSSTATE if it does not exist, so when the upgrade from CA DLP r12.0 To CA DLP r12.5 is executed the table WGN3STATSSTATE is found and the upgrade fails with the above error.
Solution:
To workaround this issue you can either: