After an OID 11g Node Restart, LDAP Replication Stopped Working | "remtool -pverify" Hangs | Log Errors May Include: Unable to read replication configuration information / ERR:Can't contact LDAP server / gslrrcbChangeRetryProc:Failed to get attribute
(Doc ID 1663703.1)
Last updated on NOVEMBER 13, 2019
Applies to:Oracle Internet Directory - Version 11.1.1 and later
Information in this document applies to any platform.
Oracle Internet Directory (OID) 11g, e.g. 184.108.40.206.0 version, using OID LDAP Replication Server.
Directory Replication Group (DRG) consisting of three OID configured in Enterprise Manager (EM) for multimaster replication:
oidhost1 - Main Production node
oidhost2 - Second Production node
droidhost3 - Disaster Recovery (DR) node
OID on oidhost2 was restarted in one of the nodes (due to low memory on the server).
Since then, replication is broken. The OIDREPLD processes seem to be running, but no replication changes are going through.
Going to EM on oidhost1, it shows there is no replication agreement, but in Oracle Directory Services Manager (ODSM) the replication agreement exists and is visible.
Before restarting the node on oidhost2, it was receiveing updates from oidhost1, but oidhost1 was not getting any updates from oidhost2 since oidhost1 was last restarted a couple of weeks back. Also, the DR node droidhost3 has not been receiving updates for over three weeks.
After restarting oidhost2, it is not getting any updates from oidhost1 anymore either.
In addition, had to manually kill all the OID processes because opmnctl was not able to shut them down cleanly.
Running "remtool -pverify -v" hangs:
No errors on the DR node OID logs, but also noticed they have not been updated in weeks or months.
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