HP-UX Directory Server 8.1 administrator guide

Changes cannot be saved for entries with multivalued RDNs.
Opening the entry in the advanced mode shows that the naming attribute has been set to
nsuniqueid uid. However, the entry cannot be changed or corrected by changing the user ID
and RDN values to something different. For example, if jdoe was the user ID and it should be
changed to jdoe1, it cannot be done from the Console. Instead, use the ldapmodify command:
dn: cn=John Doe
changetype: modify
replace: uid
uid: jdoe
dn: cn=John Doe
changetype: modrdn
newrdn: uid=jdoe1
deleteoldrdn: 1
8.18.1.2 Renaming an entry with a single-valued naming attribute
To rename an entry that has a single-valued naming attribute:
1. Rename the entry using a different naming attribute, and keep the old RDN. For example:
ldapmodify -D "cn=directory manager" -w secret -p 389 -h server.example.com
dn: nsuniqueid=66446001-1dd211b2+dc=pubs,dc=example,dc=com
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 "cn=directory manager" -w secret -p 389 -h server.example.com
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 "cn=directory manager" -w secret -p 389 -h server.example.com
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 “Managing entries from the command
line” and the HP-UX 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.
388 Managing replication