System information

Important Information
Part Number 817-5216 Page 13 of 32
❍
The list of allowed attributes of the ipHost objectclass no longer includes o $ ou $ owner
$ seeAlso $ serialNumber.
❍
The list of mandatory attributes for the ieee802Device objectclass no longer includes cn.
❍
The list of allowed attributes for the ieee802Device objectclass no longer includes
description $ l $ o $ ou $ owner $ seeAlso $ serialNumber.
❍
The list of mandatory attributes for the bootableDevice objectclass no longer includes cn.
❍
The list of allowed attributes for the bootableDevice objectclass no longer includes
description $ l $ o $ ou $ owner $ seeAlso $ serialNumber.
❍
The OID of the nisMap objectclass is now 1.3.6.1.1.1.2.9.
When migrating from Directory Server 5.1 to 5.2, the old version of this file is migrated to
avoid potential inconsistency between the schema and the database. If you have not
customized this file, and if your database does not refer to the schema contained within it,
you can remove it from your 5.1 schema before performing the migration. This will enable
you to have a version of the file that conforms to rfc2307.
If you have customized this file, or if your database refers to the schema contained within
it, perform the following steps:
❍
For zip installations, remove the 10rfc2307.ldif file from the 5.1 schema directory and
copy the 5.2 11rfc2307.ldif file to the 5.1 schema directory. (5.1 Directory Server Solaris
packages already include this change.)
❍
Copy the following files from the 5.2 schema directory into the 5.1 schema directory,
overwriting the 5.1 copies of these files:
11rfc2307.ldif, 50ns-msg.ldif, 30ns-common.ldif,
50ns-directory.ldif, 50ns-mail.ldif, 50ns-mlm.ldif, 50ns-admin.ldif,
50ns-certificate.ldif, 50ns-netshare.ldif, 50ns-legacy.ldif, and
20subscriber.ldif.
NOTE: This issue also impacts replication. See the Replication section for more
information.
• To use SASL Kerberos authentication on Solaris platforms, you must ensure that DNS is
configured.
• On Linux systems, the combined configured cache values should not exceed 600MB.