OID Attributes Disappear After Schema Import

Question

I'm running OID 11.1.1.5, and am importing the schema of another OID instance (10g). I had originially tried to import the whole schema - took all the attributes and object classes and imported them in one ./ldapmodify command via file with the correct format:
output schema:
./ldapsearch -h <> -D <> -w <> -p <> -b cn=subschemaSubentry -s base -v "objectclass=*"
import schema:
./ldapmodify -h <> -D <> -w <> -p <> -c -f <>
the file format looked like so for each attribute and object class:
dn: cn=subschemasubentry
changetype: modify
add: attributetypes
attributetyptes: ( <nnn> NAME ' ' SYNTAX ' ' SINGLE VALUE )
dn: cn=subschemasubentry
changetype: modify
add: objectclasses
objectclasses: ( <nnn> NAME '' SUP tup STRUCTURAL MUST ( ) MAY ( ) )
After running this file I saw the following behavior:
- many of the attempts returned "object / attribute already in use"
- the attributes were no longer viewable in the schema tab
- i could see the object classes that were imported
- the object classes contained entries of the attributes that were supposed to be created
- attributes within the object class contained none of the required values (OID, Syntax, etc)
- when i tried to edit the attributes from within the object classes, it throws an error and all attributes disappear from the objectclass
- OID becomes hosed
I have a full backup of the instance that I revert to while trying to debug this issue. My questions are-
1. Has anyone else run into this?
2. Any idea what the root cause is?
3. If so, how do you recover?
4. Is OID recoverable after this kind of behavior, or is a restore required?

Answer 1

Looks like I was able to resolve my issue! Some of the attribute add fields had a SPACE in after the quote in the DESC value.
Rather than:
DESC 'some description'
It had:
DESC ' some description'
Hope that helps another poor soul. This led to major application-wide destruction if not done correctly; very little error checking on the scripts side.