My Oracle Support Banner

Streams Apply Error Queue Gets Cleared When Transactions Failed Due To Referential Integrity Constraints Are Re-Executed (Doc ID 1341290.1)

Last updated on FEBRUARY 19, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 10.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.


Apply process encountered an error due to a referential integrity violation. The error queue contains either

"ORA-02292-"integrity constraint (%s.%s) violated - child record found"


"ORA-02291- "integrity constraint (%s.%s) violated - parent key not found"

If a re-execution of the error transaction is attempted, without correcting the referential integrity , the following messages are noticed and the transaction not applied.

ERROR at line 1:
ORA-02091: transaction rolled back
ORA-02292: integrity constraint (%s) violated - child record found
ORA-06512: at "SYS.DBMS_APPLY_ERROR", line 153
ORA-06512: at "SYS.DBMS_APPLY_ERROR", line 271
ORA-06512: at "SYS.DBMS_APPLY_ADM", line 477


One would expect the error transaction to be still present in the apply error queue, but the transaction is actually removed from the error queue




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.