Last updated on APRIL 17, 2017
Applies to:Oracle Directory Server Enterprise Edition - Version 6.0 and later
Information in this document applies to any platform.
If the replication manager password is changed on Directory Server Enterprise Edition 6.x it can have the undesired effect of breaking existing replication agreements.
On the Master side you can see
[20/Aug/2010:08:04:22 -0700] - INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - Replication bind to consumer s-6000b-t6300e-zone6-sca11:25263 failed:
[20/Aug/2010:08:04:22 -0700] - INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - Failed to connect to replication consumer s-6000b-t6300e-zone6-sca11:25263
[20/Aug/2010:08:04:22 -0700] - ERROR<8318> - Repl. Transport - conn=-1
op=-1 msgId=-1 - [S] Bind failed with response: Failed to bind to remote (900).
On the Replica side you can see
[20/Aug/2010:08:08:11 -0700] conn=133361 op=0 msgId=1 - BIND dn="cn=replication manager,cn=replication,cn=config" method=128 version=3
[20/Aug/2010:08:08:11 -0700] conn=133361 op=0 msgId=1 - RESULT err=49 tag=97 nentries=0 etime=0
***Checked for relevance on 29-07-2013***
The following procedure shows an existing, working replication agreement which is then broken by changing the password within the agreement.
'dsconf accord-repl-agmt' and not to change the password within the agreement as shown in the "Breaking Replication" section below. For demonstration purposes ldapmodify is used. It should be noted that the use of ldapmodify to change the replication manager password is deprecated in DS 6.x and is only used for demonstration purposes.
Example of 'dsconf accord-repl-agmt'
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms