Replicat Exceptions Handling on Conflict Results in BLOB Content Invalid / Corrupt in Exceptions Table
(Doc ID 2781598.1)
Last updated on JULY 20, 2024
Applies to:
Oracle GoldenGate - Version 12.2.0.1.0 and laterInformation in this document applies to any platform.
Symptoms
OGG 12.2 replicat is configured with exceptions handling for a table with BLOB column (BASICFILE). Replicat successfully replicates the BLOB content to the 11g target table when there is no conflict, but on occurrence of a conflict and subsequent insert into exceptions table, the BLOB content is invalid / corrupt in the exceptions table i.e. BLOB content of scanned images can't be opened and viewed as a .jpg extension.
On handling the exception, the following is also reported in the replicat report file and ggserr.log:
OGG-02154 Skipping Conflict detection resolution for partial_lob_data.
OGG-00888 SQL statement executed successfully on interval.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |