OBIA 11g Duplicate Records in Pegging Details Fact
(Doc ID 2068288.1)
Last updated on JANUARY 30, 2017
Applies to:Business Intelligence Applications Consumer - Version 18.104.22.168.1 and later
Information in this document applies to any platform.
On : 22.214.171.124.1 version, DataWarehouse
There are duplicate records in Pegging Details Fact receiving the following error:-
ODI-1217: Session SILOS_SIL_PEGGINGDETAILSFACT (17347500) fails with return code 20000.
ODI-1226: Step Run SIL_PeggingDetailsFact.W_PEGGING_DETAILS_F fails after 1attempt(s)
ODI-1240: Flow Run SIL_PeggingDetailsFact.W_PEGGING_DETAILS_F fails while performing a Integration operation. This flow loads target table W_PEGGING_DETAILS_F.
ODI-1228: Task SIL_PeggingDetailsFact.W_PEGGING_DETAILS_F (Integration) fails on the target ORACLE connection BIAPPS_DW.
Caused By: java.sql.SQLException: ORA-20000: Error creating indexes inparallel, see W_ETL_EVENT_LOG for details
ORA-06512: at line 119
PCV/123 work order number from ASCP, The W_PEGGING_DETAILS_FS table has only one record but in the W_PEGGING_DETAILS_F Fact table there could be 5 records in total. This is due to passing only Work Order Number at the time of Work Order WID resolution.
The lookup condition in W_WORKORDER_D in SIL_PeggingDetailsFact should result in only a single record for ASCP Planning records.
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