Home | Previous Page | Next Page   Appendix A. Command-Line Utility Reference >

cdr stop

The cdr stop command stops Enterprise Replication processing.

Syntax

Read syntax diagramSkip visual syntax diagram                                (1)
>>-cdr stop--| Connect Option |--------------------------------><
 
Notes:
  1. See page Connect Option.

Usage

In most situations, Enterprise Replication starts when cdr define server is first executed. The replication threads remain running until the database server is shut down or until the local database server is deleted with the cdr delete server command. If you shut down the database server while Enterprise Replication is running, replication begins again when you restart the database server.

Under rare conditions, you might want to temporarily stop the Enterprise Replication processing without stopping the database server. The cdr stop command shuts down all Enterprise Replication threads 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.

After issuing the cdr stop command, replication threads remain stopped (even if the database server is stopped and restarted) until you issue a cdr start command.

You cannot delete a server from the enterprise if it is stopped. To delete a server with cdr delete server, you must issue a cdr start command first.

Warning:
If you issue cdr stop and database activity continues, the database server from which the command is issued and the other database servers participating in replicates will become inconsistent. To ensure consistency, verify that no database update activity occurs while Enterprise Replication is stopped.

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

See Also

Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]