[
https://issues.apache.org/jira/browse/DIRSERVER-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265181#comment-16265181
]
Jeremy Jackson commented on DIRSERVER-2213:
-------------------------------------------
Ya this is what I was thinking might happen.
Currently, we only have about 200 entries, but the real issue is the project go
live date of December 1st. Introducing a possible change that could wipe out
the ldap is not ideal.
Here's what I've tested so far, and I think it's working, but haven't tested my
application against it.
1. Create new attribute in schema editor
2. Save project and export single file ldif for Apache ds
3. On server, export complete DIT ldif
4. Import new schema file and uncheck ‘update existing entries’
a. New attributes should be added to gcbipb-custom (schema element)
5. Delete object class from gcbip-custom
6. Re Import new schema file and select update existing entries
a. Object class should be back with new MAY attributes
7. Import backup ldif file, and select update existing entries.
Do you see any fundamental issues with this, or could the same behaviour you
outlined previously, still be at play here?
Thanks
Jeremy Jackson
Business Intelligence Consultant / Consultant d'intelligence d'affaires
IBM Cognos Infrastructure Administrator/ Administrateur Infrastructure IBM
Cognos
Business Intelligence Competency Centre - Centre de compétence d'informatique
décisionnelle
613-293-4288 - Mobile
[email protected]
> Importing LDIF via Apache Directory Studio generates error
> ----------------------------------------------------------
>
> Key: DIRSERVER-2213
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2213
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: ldap
> Affects Versions: 2.0.0-M23
> Environment: Windows server 2012
> Reporter: Jeremy Jackson
> Priority: Blocker
>
> After installing Apcheds on windows and using Directory Studio to import
> LDIF, I continually receive the following type error messages:
> {noformat}
> # nga-admin, bicc_admin, groups, gcbipb
> #!RESULT ERROR
> #!CONNECTION ldap://160.106.131.42:10389
> #!DATE 2017-11-09T14:08:19.252
> #!ERROR [LDAP: error code 32 - NO_SUCH_OBJECT: failed for MessageType :
> ADD_REQUEST
> Message ID : 15
> Add Request : Entry
> dn[n]: uid=nga-admin,cn=bicc_admin,ou=groups,o=gcbipb
> objectClass: top
> objectClass: person
> objectClass: organizationalPerson
> objectClass: inetOrgPerson
> objectClass: gcbipb-Client
> TenantPrimary: 1000
> cn: Nga Tran
> creatorsName: 0.9.2342.19200300.100.1.1=admin,2.5.4.11=system
> subschemaSubentry: cn=schema
> userPassword: 0x7B 0x53 0x53 0x48 0x41 0x7D 0x7A 0x74 0x6C 0x6F 0x66 0x7A
> 0x41 0x45 0x55 0x2F ...
> entryUUID: bfcc7260-f921-4a50-9b49-8f2a519bfd6d
> uid: nga-admin
> pwdHistory: 0x32 0x30 0x31 0x37 0x31 0x31 0x30 0x38 0x32 0x31 0x30 0x31 0x30
> 0x33 0x2E 0x31 ...
> TenantSecondary: 9993
> nbSubordinates: 0
> entryParentId: 3a33a4c1-5ad2-46f7-81ba-0653dd943fb4
> nbChildren: 0
> createTimestamp: 20171108210103.102Z
> entryCSN: 20171108210103.102000Z#000000#001#000000
> sn: Tran
> entryDN: uid=nga-admin,cn=bicc_admin,ou=groups,o=gcbipb
> : ERR_251_PARENT_NOT_FOUND Parent cn=bicc_admin,ou=groups,o=gcbipb not found]
> {noformat}
> .
> I'm trying to create a backup and restore procedure, but I'm unable to import
> an exported ldif file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
