AnsweredAssumed Answered

Question on Incremental Load Data Warehouse Failures

Question asked by alanbrobst on Mar 21, 2018
Latest reply on Mar 21, 2018 by Suman Pramanik

Regarding the "Load Data Warehouse" job when run in incremental mode -- we are a SaaS environment and are having recurring issues with the job failing on the key violation shown below.  (Yes, I have a ticket open with CA Support.)  My question is, when this error occurs, does the job stop dead in its tracks, or does it continue on to its normal conclusion, reloading additional tables AFTER the error occurs?

 

I'm trying to figure out if this failure only impacts 1 table (i.e., the one in the failure statement), or many tables (i.e., that one plus every other table that would follow in the ETL sequence).

 

Does anyone know?  Any info would be much appreciated!

 

Reload Facts 1? - An error occurred executing this job entry :  Couldn't execute SQL: BEGIN   DWH_INV_TASK_PERIOD_FACTS_LOAD (P_ARRAY_SIZE => 50000); END;  [CA Clarity][Oracle JDBC Driver][Oracle]ORA-20100: ENCOUNTERED EXCEPTION WHILE INSERTING INTO DWH_INV_TASK_PERIOD_FACTS_LOAD. SQLERRM : ORA-20100: ENCOUNTERED EXCEPTION WHILE INSERTING INTO DWH_INTERNAL_MD. SQLERRM : ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found ORA-06512: at "SC51432PDWH.DWH_INV_TASK_PERIOD_FACTS_LOAD", line 56 ORA-06512: at line 2

Outcomes