OUD11g/12c - Using "ldapdelete" Command with "managedsait" Control Crashes Replication with "Could not replay operation DeleteOperation with ChangeNumber error Other Database exception: (JE 7.0.7) Environment must be closed"
(Doc ID 2770538.1)
Last updated on OCTOBER 26, 2021
Applies to:
Oracle Unified Directory - Version 11.1.2.3.0 and laterInformation in this document applies to any platform.
Symptoms
In a replication topology, while performing delete operation with control managedsait
$OUD_INSTANCE/bin/ldapdelete -p <PORT> -h <HOSTNAME> -D "<DS_ADMIN>" -j pwd.txt --control managedsait -c -f /tmp/entries_to_del.ldif
the replication stopped working. Then during a stop-ds operation, the database is reported as closed/disabled:
[30/Feb/2021:10:00:03 +0000] category=SYNC severity=MILD_ERROR msgID=NNNNNNN msg=Could not replay operation DeleteOperation(connID=-1, opID=NNNN, dn=cn=<ENTRY_DN>) with ChangeNumber XXXXXXXXXXXX error Other Database exception: (JE 7.0.7) Environment must be closed, caused by: com.sleepycat.je.ThreadInterruptedException: Environment invalid because of previous exception: (JE 7.0.7) <PATH_TO>/OUD/db/app java.lang.InterruptedException THREAD_INTERRUPTED: InterruptedException may cause incorrect internal state, unable to continue. Environment is invalid and must be closed.
Changes
No changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |