Parallel Replicat Non-Integated May Shift Leading And Trailing CLOB Chars While Applying On Target
(Doc ID 2768375.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle GoldenGate - Version 19.0.0.0.0 to 19.1.0.0.4 [Release 19]Information in this document applies to any platform.
Symptoms
This is a behavior observed when using Parallel Replicat in Non-Integrated mode only.
It is not easy to catch as it deals with CLOB character content getting shift one byte to the right due to an unexpected '0-char' appended at the beginning of the string. Therefore the last byte is missed. Here the example to clarify:
Consider the hypothetical scenario where a CLOB column has following content at source:
SOURCE :
DUMP(TO_CHAR(VAL_DOC_CLINQ))
--------------------------------------------------------------------------------
Typ=1 Len=90:
95,68,83,81,82,69,80,79,82,84,66,69,71,73,78,95,160,10,160,10,160,10,160,10,82,32,65,68,95
The same output on target after applying above change via PR non-integrated will show:
select dump(to_char(MY_CLOB_COL)) from MY_CLOB_TABLE;
DUMP(TO_CHAR(VAL_DOC_CLINQ))
--------------------------------------------------------------------------------
Typ=1 Len=90:
0,95,68,83,81,82,69,80,79,82,84,66,69,71,73,78,95,160,10,160,10,160,10,160,10,82,32,65,68
You can see above an extract '0,' at the beginning of the string and the miss of last character (95: "_") at the end.
Trail file from source is consistent, and did not show any additional character, therefore the problem is happening during execution time of PR non-integrated.
Changes
Implemented Parallel Replicat in non-integrated mode.
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 |