Veridata Compare Of Ora10g to Ora11g Showing Rows OOS That Should Be In-sync
(Doc ID 1452943.1)
Last updated on MARCH 07, 2019
Applies to:
Oracle GoldenGate Veridata - Version 3.0.0.6 and laterInformation in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Symptoms
Veridata v3.0 using Java agents to compare:
Source db: 11g Enterprise Edition Release 11.1.0.7.0
Target db: 10g Enterprise Edition Release 10.2.0.5.0
with the same charaterset: WE8ISO8859P9
results in OOS char rows where column dump matches but the rows are visually
different because of extended ascii characters.
Here's the dump/convert of the OOS rows from the compare report:
SELECT DUMP(<col_name>), CONVERT(<col_name>,'UTF8','WE8ISO8859P9')
FROM <table_name> WHERE <col_name> = <value>;
Query's output on the source:
Typ=96 Len=80:
69,82,73,67,83,83,79,78,32,82,53,50,48,32,150,32,83,73,76,86,69,8
2,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,3
2, 32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,
32,32,32,32,32,32
xxxxxxxx yyyyy � zzzzzzzzz
Query output on the target:
Typ=96 Len=80:
69,82,73,67,83,83,79,78,32,82,53,50,48,32,150,32,83,73,76,86,69,8
2,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,3
2,
32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,32,
32
,32,32,32,32,32
xxxxxxxx yyyy A? zzzzzzzzz
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 |
| Cause |
| Solution |
| References |