-
Type:
Bug
-
Status: Done
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 6.0.0, 5.5.0, 4.0.0, 3.5.1
-
Fix Version/s: 6.5.0
-
Component/s: None
-
Labels:
-
Story Points:0.5
-
Support Ticket IDs:
This issue seems to only affect non string RDNs where multiples of 256 cause missing parent entries to be reported incorrectly.
for example:
dn: changenumber=1,cn=changelog,o=com dn: changenumber=2,cn=changelog,o=com dn: changenumber=3,cn=changelog,o=com ... dn: changenumber=256,cn=changelog,o=com dn: changenumber=257,cn=changelog,o=com dn: changenumber=258,cn=changelog,o=com ... dn: changenumber=512,cn=changelog,o=com
Import the data and it will fail:
[06/09/2018:13:51:03 +0100] category=TOOLS seq=55 severity=SEVERE msg=No Such Entry: The import has been aborted because the entry 'changenumber=256,cn=changelog,o=com' does not have a parent entry
This issue does not effect 2.6.x, but once upgraded to 5.5 it is not possible to rebuild indexes or re-import the data.
- is backported by
-
OPENDJ-5554 Backport OPENDJ-5423: Incorrectly reported missing parent entries cause import-ldif and index rebuilds to fail
-
- Done
-
-
OPENDJ-5566 Backport OPENDJ-5423: Incorrectly reported missing parent entries cause import-ldif and index rebuilds to fail
-
- Done
-
-
OPENDJ-5568 Backport OPENDJ-5423: Incorrectly reported missing parent entries cause import-ldif and index rebuilds to fail
-
- Done
-
-
OPENDJ-5425 Backport OPENDJ-5423: Incorrectly reported missing parent entries cause import-ldif and index rebuilds to fail
-
- Done
-