Solving Orphan Entry Conflicts - Netscape DIRECTORY SERVER 6.01 - ADMINISTRATOR Administrator's Manual

>dn: nsuniqueid=66446001-1dd211b2+dc=pubs,dc=example,dc=com
>changetype: modrdn
>newrdn: cn=TempValue
>deleteoldrdn: 0
Remove the old RDN value of the naming attribute, and the conflict marker
2.
attribute. For example:
prompt% ldapmodify -D adminDN -w passwd
>dn: cn=TempValue,dc=example,dc=com
>changetype: modify
>delete: dc
>dc: pubs
>-
>delete: nsds5ReplConflict
>-
You cannot delete the unique identifier attribute
NOTE
Rename the entry with the intended attribute-value pair. For example:
3.
prompt% ldapmodify -D adminDN -w passwd
>dn: cn=TempValue,dc=example,dc=com
>changetype: modrdn
>newrdn: dc=NewValue
>deleteoldrdn: 1
By setting the value of the
attribute-value pair
cn=
the value of the
deleteoldrdn
For more information on the
From the Command Line," on page 50 and Netscape Directory Server Configuration,
Command, and File Reference.

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.
attribute to
deleteoldrdn
TempValue. If you want to keep this attribute, you can set
attribute to .
0
command, refer to "Managing Entries
ldapmodify
Solving Common Replication Conflicts
nsuniqueid
, you delete the temporary
1
Chapter 8 Managing Replication
.
325