dsidm fails after data migration from 1.3.x to 2.x schema

[vashirov]

Is your feature request related to a problem? Please describe. Users migrating from 1.3.x to 2.x want to take advantage of using dsidm to manage their data, but unable to do so because of the differences in schema and attributes.

Describe the solution you'd like We should document differences between 2 versions and expectations of dsidm tool (objectClasses, RDN attribute, DIT structure, etc.), so that users can modify their data accordingly. And provide tools to "upgrade" their data similar to openldap migration tools that we have.

[alanorth]

Thanks @vashirov. For what it's worth, I ended up writing an awk script to migrate our 1.3.x directory server to the 1.4.x schema, which includes the RFC 2307 → RFC 2307bis schema change, as well as the new objectClass attributes. Attaching the awk script here for reference: migrate-ldif-389-ds-1.4.awk.txt, and linking to it in our institutional git repository.

Once I finally sat down to compare a 1.3.x LDIF with one from 1.4.x it was trivial to migrate it. My test 1.4.x system is running well, with all pre-existing users and groups recognized by dsidm. I suppose a 1.3.x to 1.4.x migration is mostly similar to a 1.3.x to 2.x migration.