OBIA 11g: Two Calendars With Same Row ID Causing Errors In Load
(Doc ID 2331348.1)
Last updated on FEBRUARY 18, 2019
Applies to:Business Intelligence Applications Consumer - Version 184.108.40.206.1 and later
Information in this document applies to any platform.
Two calendars with same row ID causing error in ETL
There are two calendar lines with the same ID. One is in error causing an error on the RPD load from OTBI to ERP.
The ODI error log is that a unique index could not be created because there are duplicate rows (same ID).
The row ID is not an editable field and will require a data fix to correct the row ID for one of the calendars so they are both unique.
Calendar IDs (example) are M_1111111111199 and M_1111111111182. Both have ROW_WID (example) of 9911. SQL for identifying error rows:
Error from ODI:
ODI-1228 Task TABLE_MAINT_PROC (Procedure) fails on the target ORACLE
Caused By: java.sql.SQLException: ORA-20000:Error creating Index/Constraint:
W_MCAL_YEAR_1_P1=>ORA-1452: cannot CREATE UNIQUE INDEX; duplicate keys found
ORA-6512: at line 163
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document