Veridata Failes To Identify / Use Index Columns As Keys
Last updated on JULY 17, 2017
Applies to:Oracle GoldenGate Veridata - Version 184.108.40.206.1 and later
Information in this document applies to any platform.
Veridata v11.2.1.x Jagent is not finding PK index on Sql Server 2008 when the
column order in the PK constraint is different than in the table. Compare
validation fails with 'No Matching Primary Keys Found'.
The PK index has 3 columns:
CONSTRAINT [WC_SALES_M_A_ES_PK] PRIMARY KEY NONCLUSTERED
But in the table DDL the columns are in a different order than listed in the
CREATE TABLE [dbo].[WC_SALES_M_A_ES](
[ROW_WID] [numeric](10, 0) NOT NULL,
[COUNTRY_CODE] [nvarchar](2) NOT NULL,
[MONTH_WID] [numeric](10, 0) NOT NULL,
[SALES_TYPE_WID] [numeric](10, 0) NOT NULL,
If you try to manually map the compare with these three columns, Veridata
complains with the message:
Source key column 'SALES_TYPE_WID' is not part of index 'WC_SALES_M_A_ES_PK'
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