Solving Common Replication ConflictsChapter 8 Managing Replication 3333. Rename the entry with the intended attribute-value pair. For example:prompt% ldapmodify -D adminDN -w passwd>dn: cn=TempValue,dc=example,dc=com>changetype: modrdn>newrdn: dc=NewValue>deleteoldrdn: 1By setting the value of the deleteoldrdn attribute to 1, you delete thetemporary attribute-value pair cn=TempValue. If you want to keep thisattribute, you can set the value of the deleteoldrdn attribute to 0.For more information on the ldapmodify command, refer to “Managing EntriesFrom the Command Line,” on page 54 and Netscape Directory Server Configuration,Command, and File Reference.Solving Orphan Entry ConflictsWhen a delete operation is replicated, and the consumer server finds that the entryto be deleted has child entries, the conflict resolution procedure creates a glue entryto avoid having orphaned entries in the directory.In the same way, when an add operation is replicated, and the consumer servercannot find the parent entry, the conflict resolution procedure creates a glue entryrepresenting the parent so that the new entry is not an orphan entry.Glue entries are temporary entries that include the object classes glue andextensibleObject. Glue entries can be created in several ways:• If the conflict resolution procedure finds a deleted entry with a matchingunique identifier, the glue entry is a resurrection of that entry, with theaddition of the glue object class, and the nsds5ReplConflict attribute.In such cases, you can either modify the glue entry to remove the glue objectclass and the nsds5ReplConflict attribute, to keep the entry as a normalentry, or you can delete the glue entry and its child entries.• The server creates a minimalistic entry with the glue and extensibleObjectobject classes.In such cases, you must modify the entry to turn it into a meaningful entry, ordelete it and all of its child entries.
