Stopping a Replicate

To stop the replicate, use the cdr stop replicate command. This command changes the replicate state to inactive and deletes any data in the send queue for that replicate. When a replicate is inactive, Enterprise Replication does not transmit or process any database changes.

In general, you should only stop replication when no replication activity is likely to occur for that table or on the advice of IBM® Software Support. If database activity does occur while replication is stopped for a prolonged period of time, the replay position in the logical log might be overrun. If a message that the replay position is overrun appears in the message log, you must resynchronize the data on the replication servers. For more information on resynchronizing data, see Resynchronizing Data among Replication Servers.

You cannot stop replicates that have no participants.

cdr stop replicate sales_data server1 server23

This command causes server1 and server23 to purge any data in the send queue for the sales_data replicate and stops sending data for that replicate. Any servers not listed on the command line continue to capture and send data for the sales_data replicate (even to server1 and server23).

If you omit the server names, this command stops the replicate on all servers that are included in that replicate.

If a replicate belongs to an exclusive replicate set, you must stop the replicate set to which the replicate belongs. For more information, see Exclusive Replicate Sets and Stopping a Replicate Set.

Stopping a replicate set also stops any direct synchronization or consistency checking that are in progress. To complete synchronization or consistency checking, you must rerun the cdr sync replicateset or cdr check replicateset command.

For more information, see cdr stop replicate.