Error: "ORA-08103: object no longer exists" And "ORA-00600: internal error code, arguments: [ktecgsc:kcbz_objdchk]" And "ORA-00600: internal error code, arguments: [kjbrchkpkeywait:timeout]" Executing Data Warehouse ETL (ODI)

(Doc ID 2405803.1)

Last updated on MAY 31, 2018

Applies to:

Primavera Analytics Cloud Service - Version 17.12.0.0 and later
Primavera Analytics - Version 17.12.0.0 and later
Primavera Data Warehouse - Version 17.12.0.0 and later
Information in this document applies to any platform.

Symptoms

While running the Unifier scheduled ETL, the load plan failed with the following error attempting to execute scenario "UNIFIER_LOAD_W_EPS_HIERARCHY_D_PHYSICAL":

ERROR #1
------------
ODI-1217: Session UNIFIER_LOAD_W_EPS_HIERARCHY_D_PHYSICAL (1787760) fails with return code ODI-1298.
ODI-1226: Step Physical_STEP fails after 1 attempt(s).
ODI-1240: Flow Physical_STEP fails while performing a Merge Rows-IKM Oracle Incremental Update (MERGE)- operation. This flow loads target table W_EPS_HIERARCHY_D.
ODI-1298: Serial task "SERIAL-MAP_MAIN- (10)" failed because child task "SERIAL-EU-PRIMAVERA_ANALYTICS_TGT_LS_UNIT (70)" is in error.
ODI-1298: Serial task "SERIAL-EU-PRIMAVERA_ANALYTICS_TGT_LS_UNIT (70)" failed because child task "Merge Rows-IKM Oracle Incremental Update (MERGE)- (180)" is in error.
ODI-1228: Task Merge Rows-IKM Oracle Incremental Update (MERGE)- fails on the target connection PRIMAVERA_ANALYTICS_TGT_DS.
Caused By: java.sql.SQLException: ORA-08103: object no longer exists
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:466)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:407)

Note: The temporary object being referenced should be the ODI_TGT_USER flow table created during the scenario execution (but it doesn't appear anything dropped the temp table and only the specific scenario should be using it anyway, so the error itself might not actually be referring to the object not being present).

The ETL is designed to re-execute 3 times before failure. When the ETL executed each consecutive time, the ETL failed executing the same "UNIFIER_LOAD_W_EPS_HIERARCHY_D_PHYSICAL" scenario as well as the same step, but consecutive executions generated a different error:

ERROR #2
------------
ODI-1228: Task Merge Rows-IKM Oracle Incremental Update (MERGE)- fails on the target connection PRIMAVERA_ANALYTICS_TGT_DS.
Caused By: java.sql.SQLException: ORA-00600: internal error code, arguments: [ktecgsc:kcbz_objdchk], [0], [0], [1], [], [], [], [], [], [], [], []
  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:466)
  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:407)
  at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1113)
  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:546)
  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:269)
  at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:603)
  at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:218)


With each consecutive failure of the Unifier scheduled ETL, a P6 EPPM global real-time load plan - LOAD_PLAN_REALTIME_GLOBAL - was also running and failed while executing "Load EPS Resource Role Hierarchies" with the following error:

ERROR #3
------------
"java.sql.SQLException: ORA-00600: internal error code, arguments: [kjbrchkpkeywait:timeout], [49586], [50487], [7891882], [67], [], [], [], [], [], [], []
  ORA-06512: at "SYS.DBMS_STATS_INTERNAL", line 112
  ORA-06512: at "SYS.DBMS_STATS_INTERNAL", line 242
  ORA-06512: at "SYS.DBMS_STATS_INTERNAL", line 8419
  ORA-06512: at "SYS.DBMS_STATS_INTERNAL", line 7330
  ORA-06512: at "SYS.DBMS_STATS", line 32511
  ORA-06512: at "SYS.DBMS_STATS", line 33023
  ORA-06512: at "SYS.DBMS_STATS", line 34029
  ORA-06512: at "SYS.DBMS_STATS", line 34484
  ORA-06512: at "STARUSER.GATHER_TABLE_STATS", line 16
  ORA-06512: at "STARUSER.HIER_PKG", line 281
  ORA-06512: at line 2


STEPS
-----------------------
Although specific steps to duplicate the issue are undetermined, the following steps seemed to be occurring when this issue was experienced:

  1. Execute the Unifier ETL. Note, the LOAD_PLAN_REALTIME_GLOBAL ETL for P6 should already be in a running/listening state.
  2. Note the reported issue which occurs



Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms