Solving Naming Conflicts

Entries with identical DNs may be created on separate masters if they
are created before the servers replicate the changes to each other. Upon replication,
the conflict resolution mechanism will automatically rename the second entry
created.

An entry with a DN naming conflict is renamed by including its unique
identifier, provided by the operational attribute nsuniqueid,
in its DN.

For example, if the entry uid=bjensen,ou=People,dc=example,dc=com is
created simultaneously on two masters, both will have the following two entries
after replication:

The second entry must be given a useful DN. You can delete the conflicting
entry and add it again with a non-conflicting name. However, renaming the
entry ensures that its contents have not changed. The renaming procedure depends
on whether the naming attribute is single-valued or multivalued. See the following
procedures.

To Rename a Conflicting Entry With a Single-Valued
Naming Attribute

When the naming attribute in a duplicate entry is single-valued, for
example dc (domain component), you cannot simply rename
the entry to another value of the same attribute. Instead, you must give the
entry a temporary name.

By setting the value of the deleteoldrdn attribute
to 1, you delete the temporary attribute-value pair o=TempHREntry. If you want to keep this attribute, set the value
of the deleteoldrdn attribute to 0.