Clarity upgrade fails with ORA-30556 on DWH_META_COLUMNS

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Upgrade fails on CMN_MODIFY_COLUMN_DATATYPE_SP with : ORA-30556: either functional or bitmap join index is defined on the column to be modified

STEPS TO REPRODUCE:

1. On Oracle, start upgrade from 16.1.3 to 16.2.3

Expected Results: The upgrade to complete successfully

Actual Results:

Upgrade goes from 16.1.3 to 16.2.2 and then fails on 16.2.3 part.

2/07/25 4:45 AM (ExecTask) Process - table: DWH_META_COLUMNS.xml
2/07/25 4:45 AM (ExecTask) Unable to modify column precision/scale: java.sql.SQLException: ORA-20001: Error in CMN_MODIFY_COLUMN_DATATYPE_SP - USER DOES NOT HAVE ALTER ANY TABLE / CREATE ANY TABLE / CREATE ANY INDEX / CREATE ANY TRIGGER PRIVILEGES
2/07/25 4:45 AM (ExecTask) ORA-06512: at "NIKU.CMN_MODIFY_COLUMN_DATATYPE_SP", line 511
2/07/25 4:45 AM (ExecTask) ORA-06512: at line 1
2/07/25 4:45 AM (ExecTask)
2/07/25 4:45 AM (ExecTask)
2/07/25 4:45 AM (ExecTask) SQL Text:
2/07/25 4:45 AM (ExecTask)
2/07/25 4:45 AM (ExecTask) java.sql.BatchUpdateException: error occurred during batching: ORA-30556: either functional or bitmap join index is defined on the column to be modified
2/07/25 4:45 AM (ExecTask) ORA-06512: at line 4

Environment

16.2.3

Cause

Custom index on table DWH_META_COLUMNS

Resolution

This is caused by a custom index on table DWH_META_COLUMNS.

As per best practices, all custom database objects have to be removed prior to upgrade as documented in Best practices for Database Customizations 

Workaround: Drop all custom indexes on DWH_META_COLUMNS table in Clarity database before upgrading.