Database object conflict resolution

Mastership restrictions prevent most inconsistent changes in different replicas, but some are unavoidable. To avoid many naming conflicts, the administrators for a family must create and enforce naming rules for objects. A use model that is enforced consistently across sites reduces the potential for conflicts.

For example, the administrators for a family follow these rules:
  • All location-specific objects must include a location identifier.
  • Objects that will be used at multiple replicas are all created at one replica.

When naming conflicts occur, MultiSite displays the name of the originating replica (the keysite) in the names. If this happens, you should rename the conflicting objects as soon as possible.