Re: Migration from 2.0.x -> 2.2.x, schema change

[Quanah Gibson-Mount <quanah@stanford.edu>]

--On Thursday, September 15, 2005 9:57 PM +0200 Ralf Hildebrandt 
<Ralf.Hildebrandt@charite.de> wrote:

> * Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>:
>
> > > attributetype  ( 1.3.6.1.4.1.192.6.1.3.2.4 NAME 'maxMailboxServer'
> > >       EQUALITY caseExactIA5Match
> > >       SUBSTR caseExactIA5SubstringsMatch
> > >       SYNTAX '1.3.6.1.4.1.1466.115.121.1.26' )
> >
> > You are my saviour. It worked! Thank you
>
> After that, I dumped the old LDAP tree to an LDIF file (using slapcat)
> and tried to reimport it usign slapadd. Now I'm getting:
>
> slapadd: dn="uid=skoecker,cn=Personen,dc=charite.de" (line=21): (65)
> invalid structural object class chain (pilotPerson/organizationalPerson)
> slapadd: dn="uid=dwahl,cn=Personen,dc=charite.de" (line=42): (65) invalid
> structural object class chain (pilotPerson/organizationalPerson) ...

> So what's biting me now (and why is 2.2.x so much more picky than
> 2.0.x?)

2.0.x did not properly enforce schema inheritance rules, 2.1 and later do.

I'd guess that your entries don't have things listed quite right for their 
objectClasses.  Could you post the objectClass values for one of your 
failed entries?

--Quanah


--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html

"These censorship operations against schools and libraries are stronger
than ever in the present religio-political climate. They often focus on
fantasy and sf books, which foster that deadly enemy to bigotry and blind
faith, the imagination." -- Ursula K. Le Guin