Multi-master Replication and Metadirectory 5.0

The Metadirectory 5.0 documentation states that it cannot work with a directory server configured for multi-master replication. We need to use Metadirectory since we are integrating the Directory Server with other systems. Does this mean that we'll be forced away from MMR configuration? What are some of the alternatives? Does iPlanet have any plans for supporting MMR in future versions of Metadirectory?

I think you can enable the retro changelog on a consumer replica. I'm pretty sure that works.
You might be able to enable it on a hub. You also might get it to work on a master, but the changelog on the master will contain some replication housekeeping changes that may confuse Meta Directory. I'm not sure what they are but they are obvious if you look at the changelog. If you can figure out some way to screen those changes out from Meta Directory, you might be able to use it.

Similar Messages

Multi-master replication and replica_update_ruv: unable to update

I'm running Sun ONE 5.2 DS on Solaris 8 with multi-master replication comprising of 2 masters (M1 & M2) and 2 consumer replicas (R1 & R2).
M1 sends updates to consumers R1 and R2, M2 sends updates to R2 and R1 (and offcourse M1 to M2 and M2 to M1).
Replication works well at all times. However, occasionally there are a few annoying messages in the consumers' error log files (which do not affect the replication):
INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - csnplCommit: can't find csn 4054e7710
000ffff0000
INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - ruv_update_ruv: cannot commit csn 405
4e7710000ffff0000
INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - replica_update_ruv: unable to update
RUV for replica o=asx.com.au, csn = 4054e7710000ffff0000
Has anyone come across this scenario? The explanation that I found on the web refers to 4.x Master and 5.1 DS but I do not have any of that and "Allow replicas to be 4.x compatible" is not set.
Below is the extract from "Release Notes for iPlanet Directory Server 5.1 Service Pack 1" found on the web:
"In a topology, where an iPlanet Directory Server 5.1 Service Pack 1 is a Dedicated consumer of a 4.x directory server supplier (4665571), messages of the following type will be written to the error log:
NSMMReplicationPlugin - csnplCommit: can't find csn 3d0f496f0001ffff0000
NSMMReplicationPlugin - ruv_update_ruv: cannot commit csn 3d0f496f0001ffff0000
NSMMReplicationPlugin - replica_update_ruv: unable to update RUV for replica <suffix> csn = 3d0f496f0001ffff0000
To prevent such a situation from occuring, configure the iPlanet Directory Server 5.1 Service Pack 1 instance as a Single Master (because a 5.x master may also be a consumer)."
Thanks in advance,
Erika

I have had a similar problem. and it was due to that I recreated a new replication agreement which pointed to a different server with the same id. Or to the same server with a different ID.
The solution provided by sun was to remove the reference to the old replicas in the dse.ldif and restart but it didn't work out. not even by ldapmodify on the replicas dn.
I had to reinstall...

Multi-Master-Replication between 6.3 (32bit) and 11g (64bit) possible?

Hello,
is it possible to run a multi-master-replication between a 6.3 32bit and a 11g 64bit Directory Server instance (both on linux)? I'm running into a
B1 - Client request contains an ASN.1 BER tag that is corrupt or connection aborted
message on the 'dsconf accord-repl-agmt' step, while 'dsconf info' works for both servers.
Yours
Karsten
Edited by: 813510 on 19.11.2010 01:55

MMR works between 6.3 and 11g and is platform-agnostic so it works across platforms.
Please check if the max-ber-size parameter is identical on both servers.
-Sylvain

Problem in multi master replication creation using DBA Studio -- replication

Hi,
I am trying to create multi master replication using DBA studio but facing following problem at the time of master group creation.
ORA-04052 error occured when looking up remote object SYS.SYS@CBOLDATA
ORA-00604 error occured at recursive SQL level 2
ORA-01017 invalid username/password, logon denied
ORA-02063 preceding line from CBOLDATA
If you want to know how I am trying the whole thing then here is the way I am doing comfiguration.
First I have created master site which is created successfully.
Here I have used two database named UPP817 & CBOLDATA
Step of master site creation is followed like this.
1. Master Site addition (Added both UPP817 & CBOLDATA using SYSTEM username)
2. Default User (No change is done, Default schema and password taken)
3. Master Site Schema (Added SCOTT/tiger)
4. Scheduled Link (No change is done, Default values taken)
5. Purge (No change is done, Default values taken)
6. Finished successfully
Master group creation there is three option available
1. General (Only value of Name is given)
2. Object (No object added)
3. Master Sites (It takes UPP817 by default as a master defination site then as a Master Site I have added CBOLDATA)
when I pressed on Create It gives me the error listed above.
I really appreceate your help
Mukesh

Create public database link at master site database for CBOLDATA.
Also see that you are using SNMP protocol and Oracle Pipe at both
databases. This will be usefull while making replication from remote
place.
I hope this will work.
regards
Avinash Jadhav

Multi Master Replication - Only works for some tables?

I have a multi master replication between a 9i and an 816 database.
All the tables are in the same tablespace and have the same owner. The replication user has full privs on all the tables.
When setting up the replication some tables create properly, but others fail with a "table not found" error.
Ideas anyone ?
Andrew

You said that you have a 9i replicated with a 816.
I try the same thing but with two 9i enterprise version databases, free downloaded from www.oracle.com.
when i ran
exec dbms_repcat.add_master_database(gname=>'groupname', master=>'replica_link')
this error appears
ERROR at line 1:
ORA-23375: feature is incompatible with database version at replica_link
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_REPCAT_MAS", line 2159
ORA-06512: at "SYS.DBMS_REPCAT", line 146
ORA-06512: at line 1
please help me if u have any idea.

Multi-Master Replication Limits

I'm starting new project and would like ask your opinion. They like to have multi-master replication of a single table between Chicago and Denver. A record could be written in Denver, then same row read in Chicago. The opposite is also true. Replication delay should be less than 100 ms. Load is 100 TSP
I'm not even sure is possible to replicate that fast. What technology should I look at? I heard multi-master replication is not recommended any more.
Many Thanks,
Ed Jimenez

Wich database version are you using?

Procedure to create Multi Master Replication

Hi,
can anybody help on this. How to do Multi Master replication from scarch . I used to do single master . this is the first time iam trying to do Multi-Master Replication . I am looking for doc, iam unable to find . Is ther anybody can tell how to do Multi-Master little in detail. I installed my Software and i loaded my company schema and the data on one server. I have another server ready to install software and load data.

with regards to the post "RTFM"..
in my experience the sunone/iplanet manuals are very badly written and in some cases just plain wrong..
sure start with reading the manuals, then make sure you also read the release notes and then you can still be confused in some cases....
the section on mmr in the manual has a number of mistakes last time i looked..
one reason why i think community sites, and generally available "support" are such prime requisites in choosing software...
just my 2 cents

Multi-master replication questions for iPlanet 5.0, gurus out there?

hi:
I'm using iPlanet Dir Server 5.0 and I note that many gurus out there has
been able
to get this to work, that's good, but I have yet to. I have several
questions, maybe
someone can spend a few minutes and save me hours...
I have a suffix called dc=calient,dc=net. I followed the suggestions in
the
iPlanet install guide and created 2 directory servers
a) suffix o=NetscapeRoot, at some arbitrary port, 4601
b) suffix dc=calient,dc=net, at the usual port 389.
All my searches/create/delete work fine. However, when I try to replicate
with multi-master between 2 machines, I keep getting into problems.
Here's one set of questions...
Q1: do people out there really split their tree from the o=NetscapeRoot
tree?
Q2: The admin guide says the the unit of replication is a database, and
that each replication can only have 1 suffix. Is this true? Can
a replicated db have more than 1 suffix?
Q3: If I also want to replicate the o=NetscapeRoot tree, I have to set
up yet 2 more replication agreements. Isn't this more work? If
I just lump the 2 suffixes together, wouldn't it be easier? But would
it work?
Q4: I followed the instructions to enable replicas on the masters.
But then I tried to create this cn=Replication Manager, cn=config
object.
But what is the object class of this entry? An iPlanet user has uid
as its RDN... I tried a person object class, and I added a password.
But then I keep getting error code 32, object not found in the error
log. What gives? such as
WARNING: 'get_entry' can't find entry 'cn=replication
manager,cn=config', err 32
Q5: Also, are there any access control issues with this cn=Replication
Manager,
cn=config object? By this I mean, I cannot seem to see this object
using
ldapsearch, I can only see cn=SNMP, cn=config. Also, do I have
to give all access via aci to my suffix dc=calient,dc=net? Also,
given the fact that my o=NetscapeRoot tree is at a different port (say
4601),
not 389, could this be an issue?
Q6: when replication fails, should the Dir Server still come up? Mine does
not anymore
which is strange. I keep getting things like this in my log file
[08/Nov/2001:21:49:13 -0800] NSMMReplicationPlugin - Could not send consumer
mufasa.chromisys.com:389 the bind request
[08/Nov/2001:21:49:13 -0800] NSMMReplicationPlugin - Failed to connect to
replication consumer mufasa.chromisys.com:389
But why shouldn't the dir server itself come up even if replication
fails?
steve

Hi Steve,
First, please read the 'Deployment Guide'. I think that is easier to
understand when you want to setup multi-master replication. The
'Administrator's Guide' gives you step-by-step instructions, but it may
not help you to understand how to design your directory services.
Stephen Tsun wrote:
I have a suffix called dc=calient,dc=net. I followed the suggestions in
the
iPlanet install guide and created 2 directory servers
a) suffix o=NetscapeRoot, at some arbitrary port, 4601
b) suffix dc=calient,dc=net, at the usual port 389.
All my searches/create/delete work fine. However, when I try to replicate
with multi-master between 2 machines, I keep getting into problems.I don't understand something: which backend do you want to replicate?
The one holding 'o=NetscapeRoot' or the one holding 'dc=calient,dc=net'?
Do you want to setup replication between these two instances of the
directory server (i.e. between port 4601 and 389 in your example)?
Q1: do people out there really split their tree from the o=NetscapeRoot
tree?If you have multiple directory servers installed in your environment, it
is probably worth dedicating (at least) one directory server for the
o=netscaperoot tree.
Q2: The admin guide says the the unit of replication is a database, and
that each replication can only have 1 suffix. Is this true? Can
a replicated db have more than 1 suffix?Well, it is normal, since in iDS 5.x you have 1 suffix per database.
You can, however, replicate multiple databases.
Q3: If I also want to replicate the o=NetscapeRoot tree, I have to set
up yet 2 more replication agreements. Isn't this more work? If
I just lump the 2 suffixes together, wouldn't it be easier? But would
it work?You can't lump the 2 suffixes together, because each backend has 1
suffix associated with.
Q4: I followed the instructions to enable replicas on the masters.
But then I tried to create this cn=Replication Manager, cn=config
object.
But what is the object class of this entry?Usually, it is organizationalperson or inetorgperson. In most of the
cases you want an objectclass which can have userPassword attribute.
An iPlanet user has uid
as its RDN... I tried a person object class, and I added a password.
But then I keep getting error code 32, object not found in the error
log. What gives? such asYou must have misconfigured something. Or perhaps, it is not
cn=replication manager, cn=config, but 'uid=replication manager,cn=config'
Q5: Also, are there any access control issues with this cn=Replication
Manager,
cn=config object? By this I mean, I cannot seem to see this object
using
ldapsearch, I can only see cn=SNMP, cn=config.The configuration tree is protected by ACIs, so you can not see them
using anonymous BINDs. Try binding as 'directory manager' and you will
find your entry.
Also, do I have
to give all access via aci to my suffix dc=calient,dc=net?For what purpose? For replication, it is enough to set user DN in the
replication agreement and this user can update the replicated backend.
Q6: when replication fails, should the Dir Server still come up?Yes.
Bertold

Using attribute uniqueness with multi-master replication?

Hi,
I'm trying to use attribute uniqueness in a iDS 5.1 multi-master replication env. I have created a plug-in instance for the attribute (memberID) on each directory instance (same installation on NT) and tested (if I try to create a duplicate value under the same instance I get a constraint error as expected). However if I create a entry under one instance and then create a second entry (different DN) with the same attribute value on the second instance, the entry is written with no complaints? If I create the entries with an identical DN, then the directory automatically adds nsuniqueID to the RDN of the second entry to maintain DN uniqueness but it doesn't seem to mind about duplicate values within the entry despite the plug-in?
BTW I've tested MMR and it is working and I'm using a subtree to enforce uniqueness.
Regards
Simon

Attribute uniqueness plugin only ensure uniqueness on a single master before the entry is added. It doesn't check replicated operation since they have already been accepted and a positive result was returned to the client. So in a multiMastered environment, it is still possible to add 2 identical attributes, if like you're saying you're adding the entries at the same time on both master servers.
We're working on a solution to have Attribute Uniqueness working in a multiMastered environment. But we're worried about its impact on performances we may get with it.
Regards,
Ludovic.

Two problems after reinitializing multi-master replication.

Hi,
I recently set up multi-master replication between two machines, A and B, running iDS 5.1. Everything works well until I disable replication and re-enable replication. Here's the procedure that I follow:
1. Delete agreement on machine A and B.
2. Disable the replica on machine A and B.
3. Disable the changelog on machine A and B.
4. Enable the changelog on machine A and B.
5. Enable the replica on machine A and B.
6. Create replication agreement on A and B.
7. Initialize B from A.
Problem #1:
After I follow this procedure, updates to A result in the error:

Data required to update replica "cn=rep1, cn=replica, cn="o=sylantro.com", cn=mapping tree, cn=config (host rosemary.sylantro.com, port 389)" has been purged. The replica must be reinitialized.
[07/Feb/2002:10:43:28 -0800] NSMMReplicationPlugin - Replication: Incremental update failed and requires administrator action

At this point if I re-initialize B from A, the problem ceases and everything is fine.
This problem still occurs even if I restart the server before Step 4.
Problem #2.
When I assign machine A the old replicaId of machine B and assign machine B the old replicaID of machine A in Step 5, I get the following error.

[07/Feb/2002:10:06:02 -0800] NSMMReplicationPlugin - Unable to aquire replica "cn=rep1, cn=replica, cn="o=s
ylantro.com", cn=mapping tree, cn=config (host wasrocky.sylantro.com, port 389)": the replica has the same Replica ID as this one. Replication is aborting.

The server looks like it is remembering its old replicaID.
This problem still occurs even if I restart the server before Step 4.
Any insight would be greatly appreciated.
Thanks!
Gil

For the problem #1, the error message is normal since you have actually remove the changelog. However, once you have done an initialization, Replication should work.
For the problem #2, the message is correct, because, although you have changed the ReplicaId on both server, your data still contain references to the previous replicaId both on Server A and Server B.
In general, Replica ID uniquely identify a Master in a replication topology. It should not change. The replicaID is also used in the timestamps associated with each change and they guarantee that the Replication can always distinguish 2 changes, and also can detect time synchronization issues between masters.
One way to avoid the Replica ID issue when changing ReplicaIds, is to reload the data on one server and then re-initialize the second one from the first one.
Regards,
Ludovic.

Basic Multi Master Replication doesn't work!

Hi all,
 
I am studying Oracle replication and I tried to apply multi master replication MMR between two databases: WinXp12 (master definition) and WinXp11. 
After successfully doing all the steps in the code below to replicate table SCOTT.DEPT, I inserted a row in the table in WinXp12. But I didn't see the inserted row in the remote site WinXp11. 
Where wrong was I? Anything missed? 
By the way, deferror table contains no row and DBA_JOBS has no failures. 
Thanks in advance.
 
CREATE USER REPADMIN IDENTIFIED BY REPADMIN;
GRANT CONNECT, RESOURCE, CREATE DATABASE LINK TO REPADMIN;
EXECUTE DBMS_REPCAT_ADMIN.GRANT_ADMIN_ANY_SCHEMA('REPADMIN');
GRANT COMMENT ANY TABLE TO REPADMIN;
GRANT LOCK ANY TABLE TO REPADMIN;
EXECUTE DBMS_DEFER_SYS.REGISTER_PROPAGATOR('REPADMIN');
CONN REPADMIN/REPADMIN
CREATE DATABASE LINK WINXP11 CONNECT TO REPADMIN IDENTIFIED BY REPADMIN USING 'WINXP11';
SELECT SYSDATE FROM DUAL@WINXP11 ;
-- Add jobs to WINXP11
CONNECT REPADMIN/REPADMIN@WINXP11
BEGIN
DBMS_DEFER_SYS.SCHEDULE_PUSH(
 DESTINATION => 'WINXP12',
 INTERVAL => 'SYSDATE + 1/(60*24)',
 NEXT_DATE => SYSDATE,
 STOP_ON_ERROR => FALSE,
 DELAY_SECONDS => 0,
 PARALLELISM => 1);
END;
BEGIN
DBMS_DEFER_SYS.SCHEDULE_PURGE(
NEXT_DATE => SYSDATE,
INTERVAL => 'SYSDATE + 1/24',
DELAY_SECONDS => 0,
ROLLBACK_SEGMENT => '');
END;
-- ADD JOBS TO WinXP12
CONNECT REPADMIN/REPADMIN@WINXP12
BEGIN
DBMS_DEFER_SYS.SCHEDULE_PUSH(
 DESTINATION => 'WINXP11',
 INTERVAL => 'SYSDATE + 1/(60*24)',
 NEXT_DATE => SYSDATE,
 STOP_ON_ERROR => FALSE,
 DELAY_SECONDS => 0,
 PARALLELISM => 1);
END;
BEGIN
DBMS_DEFER_SYS.SCHEDULE_PURGE(
NEXT_DATE => SYSDATE,
INTERVAL => 'SYSDATE + 1/24',
DELAY_SECONDS => 0,
ROLLBACK_SEGMENT => '');
END;
BEGIN
 DBMS_REPCAT.CREATE_MASTER_REPGROUP(
 GNAME => '"MGROUP1"',
 QUALIFIER => '',
 GROUP_COMMENT => '');
END;
BEGIN
 DBMS_REPCAT.CREATE_MASTER_REPOBJECT(
 GNAME => '"MGROUP1"',
 TYPE => 'TABLE',
 ONAME => '"DEPT',
 SNAME => '"SCOTT"');
END;
-- Generate Replication Support
BEGIN
 DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT(
 SNAME => '"SCOTT"',
 ONAME => '"DEPT"',
 TYPE => 'TABLE',
 MIN_COMMUNICATION => TRUE,
 GENERATE_80_COMPATIBLE => FALSE);
END;
SELECT * FROM DBA_REPCATLOG ;
-- NO ERROR
BEGIN
DBMS_REPCAT.RESUME_MASTER_ACTIVITY(
GNAME => '"MGROUP1"');
END;
BEGIN
DBMS_REPCAT.SUSPEND_MASTER_ACTIVITY(
GNAME => '"MGROUP1"');
END;
BEGIN
DBMS_REPCAT.ADD_MASTER_DATABASE(
GNAME => '"MGROUP1"',
MASTER => 'WINXP11');
END;
-- Restart replication support:
BEGIN
DBMS_REPCAT.RESUME_MASTER_ACTIVITY(
GNAME => '"MGROUP1"');
END;
-- here I could see in WinXP11 the tables created in SCOTT schema with data
-- in WinXP12 I successfully issued the command
insert into dept values ( 44,'text',null);
-- I don't see the data in WinXP11
-- No rows in deferror
-- dba_jobs shows that there is not broken job

Hi!
You will need to create a public db link and a private db link connecting to the public link.
CONN / AS SYSDBA
CREATE PUBLIC DATABASE LINK WINXP11 USING 'WINXP11';
CONN REPADMIN/REPADMIN
CREATE DATABASE LINK WINXP11 CONNECT TO REPADMIN IDENTIFIED BY REPADMIN;
SELECT SYSDATE FROM DUAL@WINXP11;
Regards,
PP

Streams multi master replication problem

Dear Stefan Menschel,
Good morning
DB:10.2.0.2
OS:windowsXp
This is we are trying in test environment
I have downloaded the OSC and just configured the multi master replication i mean just run the folder(400) scripts. After all the scripts exec. i was monitoring the streams activity through OEM console.
i have got an error in -->streams -->propagation-->topology
ERROR : ORA-25205: the QUEUE S1ADMIN.A_QN1_DBS2TEST does not exist
and link is showing as RED culler with some error.
hub : DBS1TEST
streamsadmin: s1admin
target1 : DBS2TEST
streamsadmin: s2admin
i might be wrong while preparing the scripts. if please let me know.
i can send you the scripts also
Thanks
Hareesh.L
DBA mailid: [email protected]
Message was edited by:
user627795

I've never seen that error, but do make sure that your Replica ID's are different (that's a requirement). Also, you might consider setting up one of the masters as a hub at first, then initialize it, and then promote it. Once you've done that, you can create the replication agreement from the second host to the first one.
Patrick

DSCC multi-master replication issue

Hello All,
I am trying to setup 2 DSCC consoles with multi-master replication enabled(cn=dscc), facing issue when I see directory server list in both dscc consoles, I see below 2 dscc instances also which should not be there(since they are ADS, should be hidden). Also the changes does not reflect immediately, takes around 30 minutes or so.
Please note I am running 2 ADS instances on one box with port no 3998 and 4000 both are master. Seek your guidance on how to fix this issue.
localhost:3998 (server not registered) - Started -
localhost:4000 (server not registered) - Started -
Below are the steps I carried out to setup multi-master replication-
On instance 1
Check the DSCC port no of instance 1
D:\ldap_server\ds6\bin>dsadm info d:\ldap_server\var\dscc6\dcc\ads
Instance Path: d:/ldap_server/var/dscc6/dcc/ads
Owner: AT0094060
Non-secure port: 3998
Secure port: 3999
Bit format: 32-bit
State: Running
Server PID: 2820
DSCC url: -
Windows service registration: Disabled
Instance version: D-A00
Enable replication-
D:\ldap_server\ds6\bin>dsconf enable-repl -h localhost -p 3998 -e -d 10 master cn=dscc
Enter "cn=Directory Manager" password:
Use "dsconf create-repl-agmt" to create replication agreements on "cn=dscc".
Setup repl agmt
D:\ldap_server\ds6\bin>dsconf create-repl-agmt -h localhost -p 3998 -e cn=dscc localhost:4000
Enter "cn=Directory Manager" password:
Use "dsconf init-repl-dest cn=dscc localhost:3998" to start replication of "cn=dscc" data.
Setup rep password
D:\ldap_server\ds6\bin>dsconf set-server-prop -h localhost -p 3998 -D "cn=directory manager" -e def-repl-manager-pwd-file:d:\rmpassword.txt
Enter "cn=Directory Manager" password:
Check the password
D:\ldap2_server\ds6\bin>dsconf get-server-prop -h localhost -p 3998 -e def-repl-manager-pwd
Enter "cn=Directory Manager" password:
def-repl-manager-pwd : {SSHA}g9OpeO2H57MH2Eq4xV5gbxVqHGzEG2VpdBSuIA==
Restart ADS to read new changes
D:\ldap_server\ds6\bin>dsadm restart d:\ldap-server\var\dscc\dcc\ads
Check suffix prop-
D:\ldap_server\ds6\bin>dsconf get-suffix-prop -h localhost -p 3998 -e cn=dscc
Enter "cn=Directory Manager" password:
all-ids-threshold : inherited (4000)
db-name : bellatonus
db-path : D:/ldap_server/var/dscc6/dcc/ads/db/bellatonus
enabled : on
entry-cache-count : unlimited
entry-cache-size : 10M
entry-count : 12
moddn-enabled : inherited (off)
parent-suffix-dn : undefined
referral-mode : disabled
referral-url : ldap://machine1:4000/cn%3Ddscc
repl-accept-client-update-enabled : on
repl-cl-max-age : 1w
repl-cl-max-entry-count : 0
repl-id : 10
repl-manager-bind-dn : cn=replication manager,cn=replication,cn=config
repl-purge-delay : 1w
repl-rewrite-referrals-enabled : off
repl-role : master
require-index-enabled : off
Run accord-
D:\ldap_server\ds6\bin>dsconf accord-repl-agmt -h localhost -p 3998 -e cn=dscc localhost:4000
To test replication manager password use-
ldapsearch -h localhost -p 3998 -D "cn=replication manager,cn=replication,cn=config" -q -b "" -s base objectclass=*namingContexts
Please enter bind password:
check the replication status
D:\ldap2_server\ds6\bin>dsconf show-repl-agmt-status -h localhost -p 3998 -e cn=dscc localhost:4000
Enter "cn=Directory Manager" password:
Configuration Status : OK
Authentication Status : OK
Initialization Status : OK
Status : Enabled
Last Update Date : Jun 13, 2012 4:04:22 PM
On instance 2
Check the DSCC port no-
D:\ldap_server\ds6\bin>dsadm info d:\ldap2_server\var\dscc6\dcc\ads
Instance Path: d:/ldap2_server/var/dscc6/dcc/ads
Owner: AT0094060
Non-secure port: 4000
Secure port: 4001
Bit format: 32-bit
State: Running
Server PID: 4264
DSCC url: -
Windows service registration: Disabled
Instance version: D-A00
Enable replication
D:\ldap_server\ds6\bin>dsconf enable-repl -h localhost -p 4000 -e -d 10 master cn=dscc
Enter "cn=Directory Manager" password:
Use "dsconf create-repl-agmt" to create replication agreements
on "cn=dscc".
Setup repl agmt
D:\ldap_server\ds6\bin>dsconf create-repl-agmt -h localhost -p 4000 -e cn=dscc localhost:3998
Enter "cn=Directory Manager" password:
Use "dsconf init-repl-dest cn=dscc localhost:3998" to start replication of "cn=dscc" data.
Setup repl password
D:\ldap_server\ds6\bin>dsconf set-server-prop -h localhost -p 4000 -D "cn=directory manager" -e def-repl-manager-pwd-file:d:\rmpassword.txt
Enter "cn=Directory Manager" password:
Check the password
D:\ldap2_server\ds6\bin>dsconf get-server-prop -h localhost -p 4000 -e def-repl-manager-pwd
Enter "cn=Directory Manager" password:
def-repl-manager-pwd : {SSHA}g9OpeO2H57MH2Eq4xV5gbxVqHGzEG2VpdBSuIA==
Restart ADS
D:\ldap_server\ds6\bin>dsadm restart d:\ldap2-server\var\dscc\dcc\ads
test replication manager password with
ldapsearch -h localhost -p 4000 -D "cn=replication manager,cn=replication,cn=config" -q -b "" -s base objectclass=*namingContexts
Please enter bind password:
D:\ldap2_server\ds6\bin>dsconf get-suffix-prop -h localhost -p 4000 -e cn=dscc
Enter "cn=Directory Manager" password:
all-ids-threshold : inherited (4000)
db-name : bellatonus
db-path : D:/ldap2_server/var/dscc6/dcc/ads/db/bellatonus
enabled : on
entry-cache-count : unlimited
entry-cache-size : 10M
entry-count : 12
moddn-enabled : inherited (off)
parent-suffix-dn : undefined
referral-mode : disabled
referral-url : ldap://machine1:3998/cn%3Ddscc
repl-accept-client-update-enabled : on
repl-cl-max-age : 1w
repl-cl-max-entry-count : 0
repl-id : 20
repl-manager-bind-dn : cn=replication manager,cn=replication,cn=config
repl-purge-delay : 1w
repl-rewrite-referrals-enabled : off
repl-role : master
require-index-enabled : off
Initialize ADS2 from ADS1 using the replication agreement:
dsconf init-repl-dest -e -i -h localhost -p 3998 cn=dscc localhost:4000
Delete
Check the replication status
D:\ldap2_server\ds6\bin>dsconf show-repl-agmt-status -h localhost -p 4000 -e cn=dscc localhost:3998
Enter "cn=Directory Manager" password:
Configuration Status : OK
Authentication Status : OK
Initialization Status : OK
Status : Enabled
Last Update Date : Jun 13, 2012 4:07:36 PM
Run insync
D:\ldap2_server\ds6\bin>insync -D "cn=directory manager" -j d:\dmpw.txt -s localhost:3998 -c localhost:4000 20
ReplicaDn Consumer Supplier Delay
cn=dscc localhost:4000 localhost:3998 0
cn=dscc localhost:4000 localhost:3998 0
cn=dscc localhost:4000 localhost:3998 0
^C
D:\ldap_server\ds6\bin>insync -D "cn=directory manager" -j d:\dmpw.txt -s localhost:4000 -c localhost:3998 20
ReplicaDn Consumer Supplier Delay
cn=dscc localhost:3998 localhost:4000 0
cn=dscc localhost:3998 localhost:4000 0
cn=dscc localhost:3998 localhost:4000 0

Replicating the ADS instance, ie cn=dscc is not supported and not supposed to work so what you are trying to do is futile.

Regarding multi master replication

hi
i am getting below error while i am doing multi master replication.
I had master 1 with some entries and now i am doing replication with master-2 which doesn't have any entries.
[21/May/2007:16:52:15 -0700] - import userRoot: Import complete. Processed 258 entries in 6 seconds. (43.00 entries/sec)
[21/May/2007:16:52:15 -0700] - INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - multimaster_be_state_change: replica dc=homedepot,dc=com is coming online; enabling replication
[21/May/2007:16:52:15 -0700] - INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - replica_reload_ruv: Warning: new data for replica dc=homedepot,dc=com does not match the data in the changelog.
Recreating the changelog file. This could affect replication with replica's consumers in which case the consumers should be reinitialized.
[21/May/2007:16:52:15 -0700] - INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - This supplier for replica dc=homedepot,dc=com will immediately start accepting client updates
[21/May/2007:16:52:15 -0700] - INFORMATION - NSMMReplicationPlugin - conn=-1 op=-1 msgId=-1 - Replica (dc=homedepot,dc=com) has been initialized by total protocol as full replica
[21/May/2007:16:52:16 -0700] - WARNING<10276> - Incremental Protocol - conn=-1 op=-1 msgId=-1 - Replication inconsistency Consumer Replica "alpha.ad.com:19940/dc=homedepot,dc=com" has a different data version. It may have not been initialized yet.
i initialized both replicas.
any help is appreciated .

As Ludovic mentioned, after you load data to the first master server, you have to initialize your second server (either it's master or read-only replica) in two ways:
1) offline (with server down)
in server 1: do db2ldif -r and save the output to file
in server 2: do ldif2db using the saved file
2) online: using GUI
I don't think that you need copy over the user schema, which should be able to replicated during replication. (please correct if wrong)

Problem in implementing "Multi-Master Replication"

Hi,
I am trying to implement "Multi-Master Replication", where both sites will try to act as Master, when Site1 is down the other site will take control and data will be updated at Site2 and vice-versa.
I have created REPADMIN user at both the site.
create user repadmin identified by repadmin;
grant connect, resource to repadmin;
execute dbms_repcat_admin.grant_admin_any_schema(‘repadmin');
grant comment any table to repadmin;
grant lock any table to repadmin;
execute dbms_defer_sys.register_propagator(‘repadmin');
Then I have created DBLink at both sites:
connect repadmin/[email protected]
create database link MYDB.WORLD
connect to repadmin identified by repadmin
using 'MYDB.WORLD';
connect repadmin/[email protected]
create private database link NAVDB.WORLD
connect to repadmin identified by repadmin using 'NAVDB.WORLD';
Then created schedules for Push and Perge jobs.
-- Add jobs to NAVDB
connect repadmin/repadmin@navdb
begin
dbms_defer_sys.schedule_push(
destination => 'MYDB.WORLD',
interval => 'SYSDATE + 1/(60*24)',
next_date => sysdate,
stop_on_error => FALSE,
delay_seconds => 0,
parallelism => 1);
end;
begin
dbms_defer_sys.schedule_purge(
next_date => sysdate,
interval => 'sysdate + 1/24',
delay_seconds => 0,
rollback_segment => '');
end;
-- Add jobs to MYDB
connect repadmin/repadmin@mydb
begin
dbms_defer_sys.schedule_push(
destination => 'NAVDB.WORLD',
interval => 'SYSDATE + 1/(60*24)',
next_date => sysdate,
stop_on_error => FALSE,
delay_seconds => 0,
parallelism => 1);
end;
begin
dbms_defer_sys.schedule_purge(
next_date => sysdate,
interval => 'sysdate + 1/24',
delay_seconds => 0,
rollback_segment => '');
end;
Then created "Master Group Site" at Site1:
connect repadmin/repadmin@navdb
BEGIN
DBMS_REPCAT.CREATE_MASTER_REPGROUP(
gname => '"GROUP1"',
qualifier => '',
group_comment => '');
END;
Add desired table object for Replication:
BEGIN
DBMS_REPCAT.CREATE_MASTER_REPOBJECT(
gname => '"GROUP1"',
type => 'TABLE',
oname => '"AUTHOR"',
sname => '"PUBS"');
END;
Set Primary Key column:
BEGIN
DBMS_REPCAT.SET_COLUMNS(
sname => '"PUBS"',
oname => '"AUTHOR"',
column_list => '"AUTHOR_KEY"');
END;
Resume Master Activity at Site1:
BEGIN
DBMS_REPCAT.RESUME_MASTER_ACTIVITY(
gname => '"GROUP1"');
END;
Add another Master Site as Site2:
connect repadmin/repadmin@navdb
BEGIN
DBMS_REPCAT.SUSPEND_MASTER_ACTIVITY(
gname => '"GROUP1"');
END;
BEGIN
DBMS_REPCAT.ADD_MASTER_DATABASE(
gname => '"GROUP1"', master => ‘MYDB.WORLD');
END;
BEGIN
DBMS_REPCAT.RESUME_MASTER_ACTIVITY(
gname => '"GROUP1"');
END;
I have executed above steps as shown in attached PDF file. Now I am trying to update one row in "Author" table and it is giving error like:
ORA-23326: object group "PUBLIC"."GROUP1" is quiesced
As per the description given for error in some help file, I am trying to suspend the activity, then it is give me same error like:
SQL> BEGIN
2 DBMS_REPCAT.SUSPEND_MASTER_ACTIVITY(
3 gname => '"GROUP1"');
4 END;
5 /
BEGIN
ERROR at line 1:
ORA-23326: object group "PUBLIC"."GROUP1" is quiesced
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.DBMS_REPCAT_MAS", line 4195
ORA-06512: at "SYS.DBMS_REPCAT", line 946
ORA-06512: at line 2
Here I am stuck up and cannot perform any DML operation on the Replicated object.
Look into the matter and suggest something if anyone can.
Thanks,
Tapan Trivedi

You're probably going to have to rethink this.
Even if your replication agreements are not encrypted, it is likely that your userPassword attributes are hashed. If they're not, you could just ask either master for the cleartext userPassword anyways, and no need to try to sniff it out of replication traffic.

Multi-master Replication and Metadirectory 5.0

Similar Messages

Maybe you are looking for