Actions On Directory Server Replication Agreement Return With "Unable To Bind" Error (Doc ID 1548745.1)

Last updated on OCTOBER 11, 2016

Applies to:

Oracle Directory Server Enterprise Edition - Version 6.3.1.1.1 to 11.1.1.7.0 [Release 6.0 to 11gR1]
Information in this document applies to any platform.
Review currency on 10/2/14

Goal

After replacing SSL certs on Server A replication broke to Server B.

 

The following messages were recorded in Server A's error log:

19/Apr/2013:07:11:09 -0500] - ERROR<8318> - Repl. Transport  - conn=-1 op=-1 msgId=-1 -  [S] Bind failed with response: Failed to bind to remote (900).
[19/Apr/2013:07:12:09 -0500] - INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 -  Received error from consumer ldapB.example.com:636 for ldap_simple_bind operation
[19/Apr/2013:07:12:09 -0500] - INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 -  Failed to connect to replication consumer ldapB.example.com:636
[19/Apr/2013:07:12:09 -0500] - ERROR<8318> - Repl. Transport  - conn=-1 op=-1 msgId=-1 -  [S] Bind failed with response: Failed to bind to remote (900).

 

Solution

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