Non-Exclusive Replicate Sets

By default, the cdr define replicateset command creates non-exclusive replicate sets.

A non-exclusive replicate set has the following characteristics:

• You can manage replicates that belong to a non-exclusive replicate set both individually and as part of the set.
• Because individual replicates in a non-exclusive replicate set can have different states, the non-exclusive replicate set itself has no state.
• You should not use non-exclusive replicate sets for replicates that include tables that have referential constraints placed on columns.
• A replicate can belong to more than one non-exclusive replicate set.

Use non-exclusive replicate sets if you want to add a replicate to more than one replicate set. For example, you might want to create replicate sets to manage replicates on the target server, table, or entire database. To do this, create three non-exclusive replicate sets:

• A set that contains the replicates that replicate to the target server
• A set that contains the replicates on a particular table
• A set that contains all the replicates

In this scenario, each replicate belongs to three non-exclusive replicate sets.