Veridata Compare Pair Failed At Mapping Validation 'No Matching Primary Keys Found' But PK Exists
(Doc ID 1558046.1)
Last updated on MARCH 06, 2019
Applies to:
Oracle GoldenGate Veridata - Version 11.2.1.0.1 and laterInformation in this document applies to any platform.
Symptoms
Veridata v11.2.1.0.1 Jagent not finding PK index on Sql Server 2008 when the column order in the PK constraint is different than the column order in the table. The compare validation fails with 'No Matching Primary Keys Found'.
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 |