cdr start

Usage

Use cdr start to restart Enterprise Replication after you stop it with the cdr stop command or replication stops for another reason, such as memory allocation problems. When you issue cdr start, Enterprise Replication activates all connections to other connected replication servers. Replication servers, replicates, and replicate sets that were suspended before the cdr stop command was issued remain suspended; no data is sent for the suspended servers, replicates, or sets.

Enterprise Replication resumes evaluation of the logical log (if required for the instance of Enterprise Replication) at the replay position. The replay position is the position where Enterprise Replication stops evaluating the logical log when replication is stopped. When replication resumes, all appropriate database transactions that occurred while replication was stopped are replicated. If replication is stopped for a prolonged period of time, the replay position in the logical log might be overwritten. If the replay position is not available, the cdr start command fails with return code 214 and event alarm 75 is raised. In this situation, you must empty the send queues and reset the replay position by running the cdr cleanstart command, and then synchronize the data.

When you run the cdr start command, event alarm 49 is generated, if that event alarm is enabled.

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