Description of problem:

We have noticed two problems in the multiimaster replication environment of
389-1.2.0 code Base.  Here are the details below.
Problem
=========
When the replica is modified (role change from HUB to Supplier), the replica id
is updated from 65535 to newly given replica id (Ex: 15151) in the dse.ldif
file. But the RUV entry in the db/memory still having the old replica id (i.e
65535 ) instead of newly provided replica id. This caused the following
problems:

1.      Supplier and consumer still having the old replica ID (65535).
2.      The replication to the consumer always starts from the Min CSN and
supplier pushes all the entries from starting (If an entry is already
replicated, the consumer just ignores it). Hence you can notice multiple log
entries for a single operation in the access log.
3.      Since the replication to consumer always starts from Min CSN, the new
entries get replicated only after processing all old entries which would lead
to delay in replication of new entries.

Kindly refer the attached document for more details .

Version-Release number of selected component (if applicable):

389-1.2.0 code Base.

How reproducible:

Kindly refer the Attached document


Actual results:

1) When the replica is modified (role change from HUB to Supplier),  the
Supplier and consumer still having the old replica Id insted of newly creaed
Replica id in the db/memory.

2) Noticed multiple logs for single MOD operation in Access log.

Expected results:

1) When the replica is modified (i.e Role change from HUB to Supplier), the RUV
entry in the db/memory needs to be updated with modified replica Id (i.e which
is Supplier replica id)

2) There should not be multiple entries for single MOD operation in access logs