Clarity PPM Upgrade Failure ORA-12008 / ORA-00942

Products

• Clarity PPM On Premise

Issue/Introduction

During the Clarity 16.4.2 upgrade process (16.4.0 to 16.4.2), the database encountered a fatal transaction failure caused by invalid dependency objects. Specifically, Oracle Materialized Views (MVs) or Zonemaps—configured for REFRESH ON COMMIT—attempted to update themselves after schema modifications, but failed because their source base tables were dropped or renamed during the upgrade.

Install log:

(ExecTask) Error Applying XOG: Failure occurred while applying CMN_EVENT_MILESTONE_OBJECT.xml
6/16/26 12:36 pm (ExecTask)  Check $NIKU_HOME/logs/xog-seeddata/out/database/CMN_EVENT_MILESTONE_OBJECT_out.xml for errors

 

CMN_EVENT_MILESTONE_OBJECT_out.xml:

Caused by: java.sql.SQLException: ORA-12008: error in materialized view or zonemap refresh path

ORA-00942: table or view does not exist

Environment

Clarity 16.4.2

Cause

A custom Oracle Materialized View with REFRESH ON COMMIT has a broken dependency — a base table or view it references no longer exists in the database after the upgrade's schema changes ran.

Oracle's behavior: Any COMMIT in any session automatically triggers a refresh of all REFRESH ON COMMIT MVs. If the base object is missing, the commit itself throws ORA-12008.

Resolution

Run DBA diagnostic queries against data dictionary views like user_mviews and all_mviews to find MVs with REFRESH ON COMMIT

Against data dictionary views like user_dependencies or all_dependencies to find based objects missing for the broken MVs. 

Once you identify the broken MV and orphaned MV log

-- Drop the broken materialized view

DROP MATERIALIZED VIEW <mv_name_from_step2>;

-- If there's also an orphaned MV log:

DROP MATERIALIZED VIEW LOG ON <base_table_name>; 

Restore back the clarity system and DB back to source release and rerun the upgrade.