Installation guide

NOTE
Manually restarting the server should only be required for Red Hat Enterprise Linux 4
systems. Other systems should restart automatically.
NOTE
The setup-ds-adm in.pl script updates both the Directory Server instances and the
local Admin Server instance. However, the Admin Server console shows the old version
number, like 8.1.4, even though it has been successfully upgraded. Restart the Admin
Server to refresh the version number.
8. Restart the Directory Server Console to make sure that the version and build numbers are
appropriately updated.
9. Check the error logs to see if there are any duplicate entries in the database.
Directory Server 8.1 allowed entries with identical DNs, but slightly different DN formats, to be
added to the directory. For example:
dn: cn=" uid=jsmith,ou=Dev0,o =Engineering0",ou=People,dc=example,dc=com
uid: jsmith
givenName: test
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetorgperson
sn: smith
cn: uid=jsmith,ou=Dev0,o=Engineering0
userPassword: secret
dn: cn=uid\= jsmith\,ou\= Dev0\,o\=Engineering0,ou=People,dc=example,dc=com
uid: jsmith
givenName: test
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetorgperson
sn: smith
cn: uid=jsmith,ou=Dev0,o=Engineering0
userPassword: secret
When these duplicate entries are migrated and their DNs are upgraded to the new, stricter DN
format, the duplicate is given a slightly differnet DN that incorporates its unique ID. After the server
upgrade, these duplicate entires can be preserved (which takes up additional space) or they can
be purged.
a. Open the error log for the instance.
vim /var/log/dirsrv/slapd-instance_name/error
b. Look for error messages related to duplicate entries. T hese messages will have the term
Duplicated entrydn or Duplicated entry in them. For example:
Chapter 5. Migrating from Previous Versions
79