Load DWH Incremental job fails with duplicate keys found on DWH_TME_ENTRY_FACTS after Fiscal roll over

book

Article ID: 192127

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Load Data Warehouse (DWH) Incremental Job fails if it's run after a fiscal rollover happens and a full load is not run.

STEPS TO REPRODUCE:

  1. Schedule Time Slicing job to run every minute, allowing Fiscal Period Rollover to occur every month.
  2. Run a DWH Full Load Before the Fiscal Rollover and it finished successfully.
  3. Make no changes to the DWH enabled attributes or any configurations.
  4. Run an incremental DWH Load after the Fiscal Rollover is complete.

Expected Results :- Incremental Load should complete successfully.

Actual Results :- Incremental Load fails with error [CA Clarity][Oracle JDBC Driver][Oracle]ORA-20100: ENCOUNTERED EXCEPTION WHILE INSERTING INTO DWH_TME_ENTRY_FACTS. SQLERRM : ORA-20100: ENCOUNTERED EXCEPTION WHILE INSERTING INTO DWH_INTERNAL_MD. SQLERRM : ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found

Cause

This is caused by Defect DE55383 (DE54887, DE48982)

Environment

Release : 15.7,15.7.1,15.8

Component : CLARITY SAAS DATA WAREHOUSE

Database: Postgres and Oracle

Resolution

Workaround: Run the DWH Full load to resolve this issue.

Upgrade to 15.8.1 to fix the issue for Postgres DB, 15.9.1 for Oracle DB 

  • Fixed in 15.8.1 for POSTGRES database
  • Fixed in 15.9.1 for ORACLE database

Additional Information

See also: Load DWH job frequently reported issues