ODSEE - Reindexing Hangs with Errors : "ERROR<20995> - ... - database failed to get entry from id2entry file (id=39589), err=12" and "ERROR<20775> - Backend Database - ... - database error 12"
(Doc ID 1390673.1)
Last updated on APRIL 18, 2022
Applies to:Oracle Directory Server Enterprise Edition - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Using ldapdelete, DELETE operations result in err=1:
or, for example:
[09/Nov/2011:15:59:24 +0530] conn=21140 op=1 msgId=2 - RESULT err=1 tag=107 nentries=0 etime=0 csn=4ebb6478001200050000
Entries can be modified by ldapmodify.
When entries modified using ldapmodify, the entry can be deleted.
Issue can not be reproduced when exporting and then importing to a new instance.
Issue occurs when backup created and then restored to a new instance.
Since modifying any attribute in the entry allows the entry to be deleted, reindexing was advised as the next step to remove any index corruption issues.
During reindex of database, reindexing does not complete and hangs at 99%:
[19/Dec/2011:18:35:12 +0530] - DEBUG - conn=-1 op=-1 msgId=-1 - libdb: Lock table is out of available lock entries
[19/Dec/2011:18:35:12 +0530] - ERROR<20995> - conn=-1 op=-1 msgId=-1 - database failed to get entry from id2entry file (id=39589), err=12
[19/Dec/2011:18:35:12 +0530] - ERROR<20775> - Backend Database - conn=4128 op=116 msgId=117 - database error 12
For specific ERROR<20775> logged (above), operation traced back in errors log shows that the operation resulted in an unindexed search:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document