Errors when importing part of an LDAP schema from an LDIF file (Sun DS)

Hi Experts!

I have some trouble getting the import of an LDIF correctly. Importing user data goes fine, but when I try to import something into the "dn: cn=schema" tree, I don't seem to be able to get it right. My guess is that either

  1. It is not possible to import an LDIF schema file and I have to do it by hand, i.e., by updating 99user.ldif or adding another file to the schema directory.

  2. It is possible, but I should use another syntax. See the code snippet for the current syntax I used. This fails with "Error adding object 'dn: cn=schema'.  The error sent by the server was:

'Already exists'.  The object is: LDAPEntry: cn=schema; LDAPAttributeSet: LDAPAttribute {type='objectclasses', values='( Portal-oid NAME 'portal' SUP top STRUCTURAL MUST cn MAY ( groep $ omgeving $ omschrijving $ startRecht $ url ) X-ORIGIN 'user defined' )'} LDAPAttribute {type='objectclass', values='top,ldapSubentry,subschema'} LDAPAttribute {type='cn', values='schema'}."

After this error, the 99user.ldif does not appear updated or changed in any way.

The basic thing that I need is to automate the update of a schema, which is needed to do a controlled roll-out of a new version of our software (which needs a schema update). I can do it by hand (by changing the 99user.ldif or by using the Sun System Server Console, but I rather do it automatically (because in the end someone else will have to do it on the production server).

Btw, the same happens when I try to import an objectclass that has changed, i.e., has one added attribute (the attribute itself does exist already).Start Free Trial

1:
2:
3:
4:
5:
6:
7:

dn: cn=schema
objectClass: top
objectClass: ldapSubentry
objectClass: subschema
cn: schema
objectClasses: ( Portal-oid NAME 'portal' SUP top STRUCTURAL MUST cn MAY ( gro
 ep $ omgeving $ omschrijving $ startRecht $ url ) X-ORIGIN 'user defined' )