cdr stop replicate
The cdr stop replicate command stops the capture, transmittal, and reception of transactions for replication.
Syntax
- 1 See Connect Option.
| Element | Purpose | Restrictions | Syntax |
|---|---|---|---|
| repl_name | Name of the new replicate. | The replicate must be active and not in an exclusive replicate set. | Long Identifiers |
| at_server_group | List of database server groups on which to stop the replicate. | The database server groups must be defined for Enterprise Replication. |
Usage
The cdr stop replicate command changes the state of the replicate repl_name to inactive (no replicated data is captured, sent or received) on the replication servers in the specified at_server_group list. In addition, this command deletes any data in the send queue for the stopped replicate. You cannot stop replicates that have no participants.
If you omit the at_server_group list, the replicate enters the inactive state on all database servers participating in the replicate and all send queues for the replicate are deleted.
If a replicate belongs to an exclusive replicate set, you cannot run cdr stop replicate to stop that individual replicate. You must use cdr stop replicateset to stop all replicates in the exclusive replicate set.
If you run this command while direct synchronization or consistency checking with repair is in progress, that repair process will stop. (Consistency checking continues; only the repair stops.) Direct synchronization and consistency checking repair cannot be resumed; you must rerun cdr sync replicate or cdr check replicate command with the --repair option.
When you run the cdr stop replicate command, an event alarm with a class ID of 61 is generated, if that event alarm is enabled.
You can run this command from within an SQL statement by using the SQL administration API.
Examples
cdr sto rep -c lake aRepl g_server1 g_server2