Veridata Compare of Ora10g to Ora11g Showing Rows OOS That Should Be In-sync

Last updated on JULY 17, 2017

Applies to:

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(DESC_NMUU_PROD), CONVERT(DESC_NMUU_PROD,'UTF8','WE8ISO8859P9')
FROM DSF.ASSTPRODAMME WHERE CODI_NMUU_PROD = 100287;

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
ERICSSON R520 � SILVER

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
ERICSSON R520 A? SILVER

Cause