Manualshelf

Troubleshooting guide

ManualsBrandsRed Hat ManualsConsumer electronicsDIRECTORY SERVER 7.1 SP7 - S
51525354555657585960
Table Of Contents
60 Novell eDirectory 8.8 SP7 Troubleshooting Guide
Thus, records that contain any reference to these objects or that try to modify these definitions
need to be commented in the LDIF error file (
err.ldf
in the example).
Some objectClasses definitions in Sun ONE do not have naming attributes. Adding these
objectClasses would result in the following error in eDirectory:
LDAP error : 80 (NDS error: ambiguous naming (-651)
This error occurs because Sun ONE does not use the same method for determining naming rules
as eDirectory.
To solve this, you can use any one of the three following options:
Option 1:
Go through each of the offending objectClasses and add a valid naming attribute to each of
them.
For example:
To add the naming attribute
[ cn ]
to the objectClass
netscapeMachineData
modify the entry
(that is emphasized in the example below) in the
err.ldf
file to include the
X-NDS_NAMING
flag as
shown below:
dn: cn=schemachangetype: modifyadd: objectClassesobjectClasses: (
2.16.840.1.113730.3.2.32 NAME ’netscapeMachineData’
DESC ’iPlanet defined objectclass’ SUP top STRUCTURAL MAY c'n ' X-
NDS_NAMING ’cn’ )-
Option 2:
Go through each of the offending objectClasses and make them AUXILIARY or ABSTRACT.
For example:
To modify the definition of objectClass
netscapeMachineData
from STRUCTURAL to
AUXILIARY, modify the
err.ldf
file entry (that is emphasized in the example below) as shown
below:
dn: cn=schemachangetype: modifyadd: objectClassesobjectClasses: (
2.16.840.1.113730.3.2.32 NAME ’netscapeMachineData’
DESC ’iPlanet defined objectclass’ SUP top AUXILIARY )-
To modify the definition of objectClass
netscapeMachineData
from STRUCTURAL to
ABSTRACT, modify the
err.ldf
file entry (that is emphasized in the example below) as shown
below:
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
.
version : 1
dn:cn=schema
changetype :modify
delete : objectclasses
objectclasses : ( 2.5.6.0 NAME ’top’ STRUCTURAL )