Check or Sync Replicate Set

Use this wizard to check for data inconsistencies between a reference server and target servers, to repair data inconsistencies, or to synchronize data to repair inconsistencies for a replicate set.

Important: Running a consistency check or synchronization can consume a large amount of space in your log files. Ensure that you have sufficient space before running this command.

Task name

Use the default task name or type a new task name.

Task

Select the action to perform on the replicate set:

Check: Run a consistency check to compare the data between a reference server and one or more target servers and generate a report that describes any inconsistencies.
Check and Repair: Run a consistency check, generate a report, and repair the inconsistent rows so that they match the rows on the reference server.
Repair inconsistencies based on the latest time stamp. Select this option to repair inconsistencies based on the latest time stamp among the participants instead of on a specified reference server. The repair task evaluates extra and mismatched rows according to the rules of the time stamp or delete wins conflict resolution rules. The option is enabled when all the replicates in the replicate set use the time stamp or delete wins conflict resolution rule. The option requires IBM® Informix® 11.70.
Sync: Synchronize data among replication servers to repair inconsistent data within a replicate.
Set the size of the send queue during synchronization. Select this option to increase the amount of memory that the send queue can use during this synchronization operation.

Frequency

Select when to perform the action:

Immediately: (Default) Perform the action right now.
Once on: Perform the action on the day that you select at the start time that you specify. For example, if you select Monday with a Start time of 5 Hours and 45 Minutes, the action occurs once on the next Monday at 5:45 a.m.
Regularly every: Perform the action on the days and at the time that you specify. For example, if you specify Monday and Wednesday with a Start time of 17 Hours and 45 Minutes, the action occurs every Monday and Wednesday at 5:45 p.m.

Limits

Check only the rows that were updated in this time period.

Select this option to check only rows that were updated since a specific time, for example, since the last consistency check. The option is enabled when all the replicates in the replicate set use the time stamp or delete wins conflict resolution rule.

Specify the time from which to check:

During the previous time period: Specify the amount of time. For example, if you select 1 hour, only the rows that were updated since 1 hour ago are checked.
Since this time: Specify the time from which to check.

Quality of data monitoring

This option is enabled when the quality of data is monitored for the replication servers for this replicate set. This option requires IBM Informix 11.70.

When the quality of data is monitored, the Connection Manager can route client connections to the replication servers based on the transaction latency, the number of apply failures, and the workload. When the quality of data is not monitored, the Connection Manager can route client connections based on the workload only. The option to monitor the quality of data is enabled on the Replication > ER Domain page with the Modify Server action. For the Connection Manager, the OpenAdmin Tool (OAT) for Informix requires IBM Informix 11.70.xC3 and the Connection Manager that is packaged with Informix 11.70.xC3 or later, or with IBM Informix Client Software Development Kit (Client SDK) 3.70.xC3

Specify how to handle the failed transactions count.

When the quality of data is monitored, the failed transactions on the replication servers are counted. When you synchronize data, you can reset the failed transaction count on the replication servers or you can continue with the current count. To maintain accurate information about the quality of data, reset the count when you synchronize the data.

Server options

Reference server: Select the database server to use as the reference copy of the data. The list displays the servers that are participants in the replicate set.

Specify how to handle rows on the target servers that are not on the reference server.

This option is not enabled when the option to repair inconsistencies based on the latest time stamp is selected.

Delete: (Default) Delete the extra rows from the target servers.
Keep: Keep the extra rows on the target servers.
Merge: Keep the extra rows on the target servers and replicate them to the source server.

Specify how to handle triggers at the target servers while synchronizing the data.

Off: (Default) Do not fire triggers at target servers during synchronization.
On: Always fire triggers at target servers even if the fire trigger option is off in the replicate definition.
Follow replication setting: Fire triggers at target servers only if the fire trigger option is on in the replicate definition.

Specify how to handle disabled replication servers while repairing the data.

This option is enabled when the Check and Repair option is selected. A replication server is disabled when replication is temporarily stopped on the server with the Disable Replication action. When replication is enabled either with this option or with the Enable Replication action, the server must be synchronized with the rest of the replication domain.

Do not enable replication: (Default)
Enable replication: Enable any disabled servers in the replicate set and synchronize the data.

Specify the number of available processes to use.

You can increase the speed of a consistency check or a synchronization on a replicate set by performing the action on the replicates in parallel. For best performance, specify the maximum number of processes. This number is either the number of available virtual processors or the number of replicates in the replicate set, whichever is smaller. This option requires IBM Informix 11.50.xC5 or later. If the number of virtual processors for the server or the number of replicates in the set is 1, the option is disabled.

Not all replicates can be processed in parallel. For example, if replicates have referential integrity rules, the replicates with the parent tables must be processed before the replicates with the child tables.

Target Servers

This list displays the names of the server groups for each participant in the replicate set. Select the server groups on which to perform the action.

To perform the action on all the server groups in the replicate set, select All target servers.