Issue 8461 - Unable to import LDIF from back-hdb DB to back-mdb db
Summary: Unable to import LDIF from back-hdb DB to back-mdb db
Status: UNCONFIRMED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: 2.7.0
Assignee: OpenLDAP project
URL:
Keywords:
: 10088 (view as issue list)
Depends on: 9009
Blocks:
  Show dependency treegraph
 
Reported: 2016-07-08 16:33 UTC by Quanah Gibson-Mount
Modified: 2023-08-08 18:32 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Quanah Gibson-Mount 2016-07-08 16:33:18 UTC
Full_Name: Quanah Gibson-Mount
Version: 2.4.39+patches
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (75.111.52.177)


In moving off of back-hdb, encountered a scenario where importing the LDIF
exported via slapcat failed when loading into back-mdb via slapadd.  There is
nothing technically wrong with the entry.  Will provide the problematic entry
elsewhere, as it contains PII.
Comment 1 OpenLDAP project 2017-03-22 16:33:32 UTC
Note: problematic DN was supplied to Howard on 7/8/2016
Comment 2 Quanah Gibson-Mount 2017-03-22 16:33:32 UTC
changed notes
moved from Incoming to Software Bugs
Comment 3 Quanah Gibson-Mount 2017-11-08 16:45:55 UTC
--On Friday, July 08, 2016 5:33 PM +0000 quanah@openldap.org wrote:

> In moving off of back-hdb, encountered a scenario where importing the LDIF
> exported via slapcat failed when loading into back-mdb via slapadd.
> There is nothing technically wrong with the entry.  Will provide the
> problematic entry elsewhere, as it contains PII.

To note, the problematic entry has an RDN value > 512 characters. 
Anonymizing the problem DN, we have:

dn="zimbraSignatureName=xxxxx xxxxxxxxxxxxx xxxxxx xx xxxx x xxxx! ..xxxxxx 
xx xxxxxxxx xxx'x xxxx xxxxx xxxxx xxxxxx… & xxxx xx x xxxxx xx xx xxxx 
xxxx xxxxx!?! …x xxxx xxxxx xx xxxxxxxxxx xxxxxxxxx xxxxxxxxx xxxxxxx: 
xxxxxx & xxxxxxxx & xxxxxx xxxxx x xxxxxx xx xxx xxxxxx 
xxxxxxx.,uid=xxxxxxxxxxxx,ou=people,dc=xxxx,dc=xx" (line=89392876): 
txn_aborted! MDB_BAD_VALSIZE: Too big key/data, key is empty, or wrong 
DUPFIXED size (-30781)


--Quanah

--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>


Comment 4 Quanah Gibson-Mount 2021-06-10 17:03:41 UTC
Depends on LMDB 1.0
Comment 5 Quanah Gibson-Mount 2023-08-02 19:31:45 UTC
*** Issue 10088 has been marked as a duplicate of this issue. ***
Comment 6 Quanah Gibson-Mount 2023-08-08 18:32:28 UTC
*** Issue 10088 has been marked as a duplicate of this issue. ***