Re: migrating from V1->V2

[Jim Howell <jwh2@cornell.edu>]

At 10:45 AM 10/3/2000 -0700, Kurt D. Zeilenga wrote:
> At 02:22 PM 10/2/00 -0400, Jim Howell wrote:
> >Hi,
> >        However after a bit more thought it occurred to me that the 
> photos and audio attributes not being "movable" may be an issue in the 
> future when openldap moves from V2->V3.
>
> We're not planning on OpenLDAP 3.0 any time soon... but note that
> OpenLDAP 2.0 implements LDAPv3.

Hi,
        Right, OpenLDAP v2 implements LDAPv3.  But that doesn't explain 
why I couldn't load the photo and audio attributes from my OpenLDAp v1 
system into my OpenLDAP v2 system.  The OpenLDAPv2->v3 move is a futures 
concern.  Not being able to transfer data from a old DB to the new DB will 
be an issue.
Jim


> > Any thought or fixes on that issue would be appreciated.  It isn't 
> going to be a make or break this time but I am concerned for the 
> future..  Thanks.
> >Jim HOwell
> >
> >
> >
> >Hi,
> >        I've been migrating my ldap server from openldap v12.11 to 
> openldap v2.0.4 on a Solaris 2.6 system and here are some of my observations:
> >
> >- I took ldif dump generated by ldbmcat from my v1 system and tried to 
> feed it into my v2 system and it barfed on the "photo" and "audio" 
> attributes.  I have the core.schema, inetorgperson.schema, and 
> cosine.schema.  Error Msg:
> >
> >modifying entry "cn=dbt1, o=Cornell University, c=US"
> >ldap_modify: Can't contact LDAP server
> >
> >ldif_record() = 81
> >
> >
> >- I also had some fields that showed up in my ldif that had no data (ex. 
> pager:   ) and it didn't like that either.  While I don't dis-agree 
> that  blank fields incorrectly take up space in the DB I thought folks 
> should know this.  Error Msg:
> >ldap_add: Protocol error
> >        additional info: no values for attribute type
> >
> >ldif_record() = 2
> >
> >
> >If I've missed something here please slap me upside the head as 
> appropriate....
> >Jim