My Oracle Support Banner

ETL Fails On SILOS_SIL_PARTYDIMENSION_ORGANIZATION Due To W_PARTY_D_P1 Constraint Violation when Diagnostics is enabled (Doc ID 2305894.1)

Last updated on AUGUST 16, 2019

Applies to:

Business Intelligence Applications Consumer - Version and later
Information in this document applies to any platform.


Diagnostic logic is not handling DATE column values correctly due to nls_date_format.

Hence, Incremental ETL load fails on SILOS_SIL_PARTYDIMENSION_ORGANIZATION due to W_PARTY_D_P1 constraint violation.


ODI-1217: Session SILOS_SIL_PARTYDIMENSION_ORGANIZATION (163883504) fails with return code 20942. ODI-1226: Step Diagnostics Raise Exception fails after 1 attempt(s). ODI-1232: Procedure Diagnostics Raise Exception execution fails. ODI-1228: Task Diagnostics Raise Exception (Procedure) fails on the target ORACLE connection BIAPPS_DW. Caused By: java.sql.SQLException: ORA-20942: ODI-1228: Task SIL_PartyDimension_Organization_Incr.W_PARTY_D (Integration) fails on the target ORACLE connection BIAPPS_DW. Caused By: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (BI11G_DW.W_PARTY_D_P1) violated at oracle.jdbc.driver.T4CTTIoer.processError( at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIo




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.