After an OID Node Restart, LDAP Replication Stops Working, "remtool -pverify" Hangs, Log Errors: "Failed to bind with server(replicaId)" "Can't Connect to Server" "failure connecting to server" "Unable to check port type" (Doc ID 1663703.1)

Last updated on JULY 14, 2023

Applies to:

Symptoms

Oracle Internet Directory (OID) using OID LDAP Replication Server which had been working.

OID on one of the hosts was restarted / rebooted (for various reason, e.g., OS patching or upgrade, low resources, etc).

Since then, replication is broken.  The OIDREPLD processes seem to be running, but no replication changes are going through, or it may be working just one way.

Example OID 12c replication log from the problem host:

No errors on a third Disaster Recovery (DR) node OID logs, but also noticed they have not been updated in weeks or months.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.