Veridata Compare Pair Failed At Mapping Validation 'No Matching Primary Keys Found' But PK Exists

(Doc ID 1558046.1)

Last updated on JULY 17, 2017

Applies to:

Oracle GoldenGate Veridata - Version and later
Information in this document applies to any platform.


Veridata v11. 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'.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms