Upgrade failure: POSTUPGRADE_CUSTOM_OBJECT_GLOBAL_COPY_RIGHT.xml

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

The upgrade to Clarity 16.1.1 fails with the following error:

7/18/24 6:42 AM (ExecTask) Process - post-upgrade: POSTUPGRADE_CUSTOM_OBJECT_GLOBAL_COPY_RIGHT.xml
7/18/24 6:42 AM (ExecTask) 
7/18/24 6:42 AM (ExecTask) SQL Text:
7/18/24 6:42 AM (ExecTask) 
7/18/24 6:42 AM (ExecTask)         DECLARE
7/18/24 6:42 AM (ExecTask)             CMO_NAME VARCHAR2(96);
7/18/24 6:42 AM (ExecTask)             CMO_COPY_RIGHT_NAME VARCHAR2(96);
7/18/24 6:42 AM (ExecTask) java.sql.BatchUpdateException: error occurred during batching: ORA-01422: exact fetch returns more than requested number of rows
7/18/24 6:42 AM (ExecTask) ORA-06512: at line 39
7/18/24 6:42 AM (ExecTask) ORA-06512: at line 39

Environment

Clarity 16.1.1 upgrade

Cause

There are some orphan records from an object previously deleted at the cmn_sec_objects table

Resolution

Here is the specific case scenario:

1. An object was created by mistake without an Investment extension association.

2. This created the following entries with a CMN component_code:

SELECT * from cmn_sec_objects where object_code LIKE 'odf_cst_myobject'

3. The object was deleted but the entries above remained orphans on the DB side

4. Afterward, a new object was created with an investment extension and the following entries were added at the DB side with an INV component_code

In 16.1.1, the upgrade creates a 'Copy' Right for existing Custom Objects and it fails at creation due to the records at the above table.

Resolution:

1. Roll back to 16.1.0

2. Update the orphan DB entries with the CMN component_code (records belonging to the object that was deleted)

3. Re-run the upgrade

Note: Do not delete the entries, rename them. Otherwise, the upgrade will still fail.