Asynchronous propagation conflicts

Enterprise Replication asynchronously propagates many control operations through the Enterprise Replication network. Avoid operations that might conflict during propagation.

When you perform administrative functions using Enterprise Replication, the status that returns from those operations indicates the success or failure of the operation at the database server to which you are directly connected. The operation might still be propagating through the other Enterprise Replication database servers in the network at that time. It might take a significant amount of time before the operation is propagated to database servers that are not connected to the Enterprise Replication network at all times.

Due to this asynchronous propagation, avoid performing control operations in quick succession that might directly conflict with one another without verifying that the first operation was successfully propagated through the entire enterprise network. Specifically, avoid deleting Enterprise Replication objects such as replicates, replicate sets, and Enterprise Replication servers, and immediately recreating those objects with the same name. Doing so can cause failures in the Enterprise Replication system at the time of the operation or later. These failures might manifest themselves in ways that do not directly indicate the source of the problem.

If you must recreate a deleted definition with the same name, run the cdr check queue command to make sure that the command is complete on all servers before recreating the definition.

You can also use a different name for the new object (for example, delete replicate a.001 and recreate it as a.002) or wait until the delete action was successfully propagated through the entire Enterprise Replication system before you recreate the object.

If you must recreate a deleted definition, use a different name for the new object (for example, delete replicate a.001 and recreate it as a.002) or wait until the delete action was successfully propagated through the entire Enterprise Replication system before you recreate the object.