Using the Replication Server set autocorrection command |
This command prevents failures caused by missing or duplicate rows in a copy of a replicated table. Autocorrection is off by default for replication definitions you create. You should enable autocorrection only for replication definitions with subscriptions that use nonatomic bulk materialization. After materialization is complete and the subscription is VALID, issue the set autocorrection off command to improve system performance. |
Using the Replication Server replicate minimal columns command |
Do not use the nonatomic bulk materialization method if you are using the replicate minimal columns option in your replication definition. Nonatomic materialization cannot be used with data for which replication definitions have the replicate minimal columns option, because autocorrection cannot resolve the inconsistencies between source and replicate data. When you use the replicate minimal columns option for a replication definition, data is replicated from the minimum number of columns needed for delete or update operations. For rows to be deleted from replicate tables, Replication Server only replicates data from primary key columns. For rows to be updated in replicate tables, Replication Server only replicates data from primary key columns and columns that changed. |
Using the Replication Server activate subscription command with the with suspension clause |
You must use the with suspension clause with the activate subscription command to prohibit updates to the primary version until after the subscription initializes. When you use the with suspension clause, the system suspends the DSI thread after changing the subscription status to ACTIVE. This prevents the replicate Replication Server from sending updates for the replicated table before the subscription data loads. After the data loads at the replicate site, you can execute the resume connection command to apply the updates. |
