Data Replication requires rows to be uniquely identified to accurately replicate Update and Delete operations.

For the source tables that do not have a primary key definition or a unique index, you can either manually create a virtual index for the source table or disable replication of Update and Delete operations. To manually create a virtual index in the Data Replication Console, select a mapped source table on the

Map Tables

tab and click the

Show Indexes

icon button. On the

Indexes

dialog box that appears, select the

Primary Key

check box.

When you save a configuration that extracts Update and Delete operations from a mapped source table that does not have a primary key definition or a unique index, the Data Replication Console prompts you to select one of the following options for replicating change data:

Create a virtual index that includes all of the mapped table columns. If a mapped column has a datatype that is not supported for additional logging, the Data Replication Console does not include this column in the virtual index.
View a list of source tables that do not have a primary key definition on the
Map Tables
tab. You can then assign a primary key or unique index definition to these tables in the source database.
Later, when you want to view a full list of the source and target tables again, click
Refresh
.
Disable replication of Update and Delete operations. In this case, Data Replication replicates only Insert operations. Also, for DB2, SQL Server, and Oracle sources, Data Replication replicates DDL changes.