Solving Orphan Entry Conflicts - Red Hat DIRECTORY SERVER 8.0 - ADMINISTRATION Administration Manual

Chapter 8. Managing Replication
changetype: modrdn
newrdn: cn=TempValue
deleteoldrdn: 0
2. Remove the old RDN value of the naming attribute and the conflict marker attribute. For example:
ldapmodify -D adminDN -w password
dn: cn=TempValue,dc=example,dc=com
changetype: modify
delete: dc
dc: pubs
-
delete: nsds5ReplConflict
-
NOTE
The unique identifier attribute nsuniqueid cannot be deleted.
3. Rename the entry with the intended attribute-value pair. For example:
ldapmodify -D adminDN -w password
dn: cn=TempValue,dc=example,dc=com
changetype: modrdn
newrdn: dc=NewValue
deleteoldrdn: 1
Setting the value of the deleteoldrdn attribute to 1 deletes the temporary attribute-value pair
cn=TempValue. To keep this attribute, set the value of the deleteoldrdn attribute to 0.
For more information on the ldapmodify command, see
Command-Line" and the Directory Server Configuration, Command, and File Reference.

8.18.2. Solving Orphan Entry Conflicts

When a delete operation is replicated and the consumer server finds that the entry to be deleted has
child entries, the conflict resolution procedure creates a glue entry to avoid having orphaned entries
in the directory.
In the same way, when an add operation is replicated and the consumer server cannot find the parent
entry, the conflict resolution procedure creates a glue entry representing the parent so that the new
entry is not an orphan entry.
Glue entries are temporary entries that include the object classes glue and extensibleObject.
Glue entries can be created in several ways:
• If the conflict resolution procedure finds a deleted entry with a matching unique identifier, the
glue entry is a resurrection of that entry, with the addition of the glue object class and the
nsds5ReplConflict attribute.
In such cases, either modify the glue entry to remove the glue object class and the
nsds5ReplConflict attribute to keep the entry as a normal entry or delete the glue entry and its
child entries.
300
Section 2.2, "Managing Entries from the