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 capture, transmit, or process any database changes.

For example, to stop the sales_data replicate on the servers server1 and server23, enter:

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.

4Stopping a replicate also stops any direct synchronization, 4consistency checking, or repair jobs that are in progress. To complete synchronization 4or consistency checking, you must rerun the cdr sync replicateset or cdr check replicateset command. To restart a 4repair job, use the cdr start repair command.

For more information, see cdr stop replicate.