cdr stop

The cdr stop command stops replication on the server to which you are connected without shutting down the database server.

Syntax


1  cdr stop %Connect Option(1)
Notes:

Usage

Generally, to stop replication on a server, you should shut down the database server. Under rare conditions, you might want to temporarily stop the Enterprise Replication processing without shutting down the database server.

The cdr stop command shuts down replication in an orderly manner; however no data to be replicated is captured. When the shutdown of Enterprise Replication is complete, the message CDR shutdown complete appears in the database server log file.

Stopping replication has the following effects:

  • There is no connection between the stopped server and active replication servers.
  • Transactions on the stopped server are not captured for replication. However, after restarting replication, transaction capture restarts at the replay position. If replication is stopped for long enough that the replay position is overwritten, you must restart replication with the cdr cleanstart command. If the CDR_LOG_LAG_ACTION configuration parameter is set to logstage, logs are staged to protect the replay position.
  • Transactions on active replication servers are queued for the stopped server, but there is the possibility of filling up the send queues.
  • Control messages on active replication servers are queued for the stopped server.
  • The only Enterprise Replication commands you can run on the stopped server are cdr start, cdr cleanstart, and cdr delete server with the --force option.

To ensure consistency, prevent database update activity while Enterprise Replication is stopped. Replication threads remain stopped until you issue a cdr start command. Shutting down and restarting the stopped database server does not restart replication.

If you plan to stop replication for a long period of time and your replicates use time stamp or delete wins conflict resolution rules, consider using the cdr disable server command instead of the cdr stop command.

When you run the cdr stop command, event alarms with class IDs of 50 and 71 are generated, if those event alarms are enabled.

You can run this command from within an SQL statement by using the SQL administration API.

Return Codes

0
The command was successful.
5
Enterprise Replication cannot connect to the specified server.
48
There is not enough memory to perform the operation.
62
Enterprise Replication is not active.
93
Enterprise Replication is in the process of starting.
94
Enterprise Replication is already in the process of stopping.

Examples

The following example stops Enterprise Replication processing on database server paris. Processing does not resume until a cdr start command restarts it: 
cdr stop -c paris