OID LDAP multi-master Replication lock results in consumer restart (Doc ID 2274084.1)

Last updated on AUGUST 16, 2017

Applies to:

Oracle Internet Directory - Version 11.1.1 to 11.1.1.9.0 [Release 11g]
Information in this document applies to any platform.

Symptoms

Some delete operations result in the consumer OID to hang, not responding to even ldapbind requests.  

Eventually the consumer oidldapd crashes,  creates a stack dump, then the oidldapd process is restarted and processing returns to normal.

This has been observed using the DBCA tool during a database de-register event, with the olsadmintool during a "droppolicy" operation, and also with ODSM and LDAPDELETE  performing the same operations.

A sample pstack output results from the oidldapd process that is hung is as follows:

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms