Clean Start Replication

Use this action to empty the replication queues of pending transactions and restart replication on an Enterprise Replication (ER) server.

Prerequisite: If the ER server was restored from a backup, but the restore did not include all log files from the replay position, or the system was not restored to the current log file, advance the log file unique ID past the latest log file unique ID. To advance the log position, switch to the next logical-log file by using the onmode -l command at the command line.

Restart replication with empty queues if the Start Replication action fails because the replay position is not available. The replay position is where ER stops evaluating the logical log when replication is stopped. If replication is stopped for a prolonged period, the replay position in the logical log might be overwritten. In this situation, use the Clean Start Replication action to empty the send queues and reset the replay position. Then synchronize the data by using the Check or Sync Replicate or Check or Sync Replicate Set action.

You can also restart replication with empty queues if synchronizing the data on the server by using a check or sync action is faster than synchronizing by allowing the queues to process normally.