Informix 9.3x Enterprise Replication
Posted in 2003
Topics: High Availability & Replication
We are in the process of configuring Informix 9.31.UC3 Enterprise Replication to consolidate data to one central server. I have successfully configured, this is all on lab systems to prove the concept, a Primary server and a Target server, named g_rep1 and g_rep2 respectively. The replicates and participants in this configuration work fine and I can update data on g_rep1 and view the changed data on g_rep2. Here are the steps I proceeded with to define these servers, but I won't bother to put the replicates in this posting. They are basically the "select * from table" for all the tables in the STORES_DEMO database. g_rep1 (Primary) ================ cdr define server -c g_rep1 -A /tmp -R /tmp -I g_rep1 g_rep2 (Target) =============== cdr define server -A /tmp -R /tmp -I -S g_rep1 g_rep2 Here are the steps I went through to include a second Primary server, g_rep3, to replicate it's data to g_rep2, the Target. g_rep2 (Target) =============== cdr stop -c g_rep2 cdr define server -A /tmp -R /tmp -I -S g_rep3 g_rep2 cdr start server Results of "cdr list server" on g_rep1, g_rep2 and g_rep3 g_rep1 (Primary) ================ [informix@linuxrep1 informix]$ cdr list server SERVER ID STATE STATUS QUEUE CONNECTION CHANGED ----------------------------------------------------------------------- g_rep1 67 Active Local 0 g_rep2 68 Active Connected 0 Jul 21 11:44:32 g_rep2 (Target) =============== [informix@linuxrep2 informix]$ cdr list server SERVER ID STATE STATUS QUEUE CONNECTION CHANGED ----------------------------------------------------------------------- g_rep1 67 Active Connected 0 Jul 21 11:44:31 g_rep2 68 Active Local 0 g_rep3 12 Active Connected 0 Jul 21 11:45:40 g_rep3 (Primary) ================ [informix@lab informix]$ cdr list server SERVER ID STATE STATUS QUEUE CONNECTION CHANGED ----------------------------------------------------------------------- g_rep2 68 Quiescent Connected 0 Jul 21 11:45:41 g_rep3 12 Active Local 0 What would take g_rep3's connection to g_rep2 so long to change from Quiescent to Active? It has been well over an hour since I issued the commands mentioned above. Have I not done something correctly, or in the wrong order? Thank you for all your assistance. Mark
See below.... "Mark Bradley" <mbradley@nmcourts.com> wrote in message news:e6db0a5a.0307211044.d9be72d@posting.google.com... > We are in the process of configuring Informix 9.31.UC3 Enterprise > Replication to consolidate data to one central server. > I have successfully configured, this is all on lab systems to prove > the concept, a Primary server and a Target server, named g_rep1 and > g_rep2 respectively. > The replicates and participants in this configuration work fine and I > can update data on g_rep1 and view the changed data on g_rep2. > > Here are the steps I proceeded with to define these servers, but I > won't bother to put the replicates in this posting. They are basically > the "select * from table" for all the tables in the STORES_DEMO > database. > > g_rep1 (Primary) > ================ > cdr define server -c g_rep1 -A /tmp -R /tmp -I g_rep1 > > g_rep2 (Target) > =============== > cdr define server -A /tmp -R /tmp -I -S g_rep1 g_rep2 > > Here are the steps I went through to include a second Primary server, > g_rep3, to replicate it's data to g_rep2, the Target. > > g_rep2 (Target) > =============== > cdr stop -c g_rep2 > cdr define server -A /tmp -R /tmp -I -S g_rep3 g_rep2 > cdr start server I don't understand this. Why are you stopping ER on g_rep2? Also, why are you then attempting to redefine ER on g_rep2? I would think that you server definitions should be somthing like... cdr define server -c g_rep1 -I g_rep1 cdr define server -c g_rep2 -I -S g_rep1 g_rep2 cdr define server -c g_rep3 -I -S g_rep1 g_rep3 The 'sync' server is not used to define source/target. The define replicat does that. The main purpose of the '-S' option is to define the server that ER will used to copy the syscdr database from when defining ER on a new server. M.P. > > > Results of "cdr list server" on g_rep1, g_rep2 and g_rep3 > > g_rep1 (Primary) > ================ > [informix@linuxrep1 informix]$ cdr list server > SERVER ID STATE STATUS QUEUE CONNECTION > CHANGED > ----------------------------------------------------------------------- > g_rep1 67 Active Local 0 > g_rep2 68 Active Connected 0 Jul 21 11:44:32 > > > g_rep2 (Target) > =============== > [informix@linuxrep2 informix]$ cdr list server > SERVER ID STATE STATUS QUEUE CONNECTION > CHANGED > ----------------------------------------------------------------------- > g_rep1 67 Active Connected 0 Jul 21 11:44:31 > g_rep2 68 Active Local 0 > g_rep3 12 Active Connected 0 Jul 21 11:45:40 > > g_rep3 (Primary) > ================ > [informix@lab informix]$ cdr list server > SERVER ID STATE STATUS QUEUE CONNECTION > CHANGED > ----------------------------------------------------------------------- > g_rep2 68 Quiescent Connected 0 Jul 21 11:45:41 > g_rep3 12 Active Local 0 > > What would take g_rep3's connection to g_rep2 so long to change from > Quiescent to Active? It has been well over an hour since I issued the > commands mentioned above. Have I not done something correctly, or in > the wrong order? > > Thank you for all your assistance. > Mark