Novell eDirectory 8.8 Troubleshooting Guide - NetIQ

dn: cn=schemachangetype: modifyadd: objectClassesobjectClasses: (
2.16.840.1.113730.3.2.32 NAME ’netscapeMachineData’
DESC ’iPlanet defined objectclass’ SUP top ABSTRACT )-
Option 3:
Add cn to the definition of Top in eDirectory, which causes a potential naming attribute for all
objectClasses.
There are two ways of adding cn to Top:
• Method 1:
Create a file as shown below and name it topsch.ldf.
novdocx (en) 11 July 2008
version : 1
dn:cn=schema
changetype :modify
delete : objectclasses
objectclasses : ( 2.5.6.0 NAME ’top’ STRUCTURAL )
-
add:objectclasses
objectclasses : (2.5.6.0 NAME ’top’ STRUCTURAL MAY cn)
Use the following Novell Import Conversion Export command line:
ice -SLDIF -f LDIF_file_name -DLDAP -s eDirectory_server -p
eDirectory_port -d eDirectory_Admin_DN -w eDirectory_password
For example:
ice -SLDIF -f topsch.ldf -DLDAP -s edir_srv2 -p edir_port2 -d
cn=admin,o=org -w pwd1
• Method 2:
1. In Novell iManager, click the Roles and Tasks button Description: Roles and Tasks
button .
2. Click Schema > Add Attribute.
3. In the Available Classes list, select Top, then click OK.
4. Double-click CN in the Available Optional Attributes list.
5. Click OK.
• Some objectClass definitions contain userPassword as part of their mandatory attributes list.
Adding such objectClasses to eDirectory cause the following error:
LDAP error : 16 (No such attribute)
To resolve this error, modify the objectClass definition to inherit the new objectClass from
ndsLoginProperties and remove the userPassword attribute from the mandatory attribute list.
For example:
An objectClass containing userPassword in the mandatory attributes list:
Migrating to Novell eDirectory 51