Enterprise Replication issues
Hi, IDS version 11.50.FC6 OS version: Solaris 10 I have 3 servers A, B and C A is replicating to B using Enterprise Replication B is replicating to C using Enterprise Replication From B to C, I replicate only a subset of tables with a different structure. When I insert a new row in A, it gets correctly replicated to B but the corresponding row does NOTget replicated to C. However when I insert a row into B, it gets replicated to C. Am I missing something? Should I define B twice: once as a secondary for A and one more time as a primary for C? Thanks _________________________________________________________________ MSN Dating: Find someone special. Start now. http://go.microsoft.com/?linkid=9729707
Hello. Could you post here you replicates / replicateset configurations, from the three servers ? Maybe something wrong related on your ER topology. Best regards. Alexandre Marini Tecnologia da Informação - DBA SEFAZ-MS / SGI-UIMP / Sistemas IBM-Informix <cid:part2.02070901.02070005@fazenda.ms.gov.br> IBM Informix Dynamic Server Certified Professional V10 / V11 Contacte-me Linkedin <http://br.linkedin.com/pub/alexandre-marini/4/606/714>; --- @ WiseStamp Signature <http://my.wisestamp.com/link?u=5pyh9cbdjqrjbm83&site=www.wisestamp.com/email-in stall>. Get it now <http://my.wisestamp.com/link?u=5pyh9cbdjqrjbm83&site=www.wisestamp.com/email-in stall> Em 4/5/2010 10:56, Georges Martin escreveu: > Hi, > > IDS version 11.50.FC6 > > OS version: Solaris 10 > > I have 3 servers A, B and C > > A is replicating to B using Enterprise Replication > > B is replicating to C using Enterprise Replication > > > From B to C, I replicate only a subset of tables with a different structure. > > When I insert a new row in A, it gets correctly replicated to B but the > corresponding row does NOTget replicated to C. > > However when I insert a row into B, it gets replicated to C. > > Am I missing something? > > Should I define B twice: once as a secondary for A and one more time as a > primary for C? > > Thanks > > _________________________________________________________________ > MSN Dating: Find someone special. Start now. > http://go.microsoft.com/?linkid=9729707 > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > > >
You're confusing topology with replication ... ;-) You define the endpoints of replication when defining the replicates. = You define the topology when defining the servers. If you want to replicate from a to [b,c], then you need to define a sin= gle replicate with three nodes, not two replicates with two nodes each. = From: "Georges Martin" <georges_martin_1@hotmail.com> = = To: ids@iiug.org = = Date: 05/04/2010 09:56 AM = = Subject: Enterprise Replication issues [19982] = = Sent by: ids-bounces@iiug.org = = Hi, IDS version 11.50.FC6 OS version: Solaris 10 I have 3 servers A, B and C A is replicating to B using Enterprise Replication B is replicating to C using Enterprise Replication >From B to C, I replicate only a subset of tables with a different structure. When I insert a new row in A, it gets correctly replicated to B but the= corresponding row does NOTget replicated to C. However when I insert a row into B, it gets replicated to C. Am I missing something? Should I define B twice: once as a secondary for A and one more time as= a primary for C? Thanks _________________________________________________________________ MSN Dating: Find someone special. Start now. http://go.microsoft.com/?linkid=3D9729707 ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =
To clarify what Madison is saying, there are a couple of points: - ER doesn't cascade. If A replicates a table to B and B replicates that target table as a source to C data updated on A will not replicate to C. - You have to define a replicant from A to C for each of the subset of tables that you want maintained on C. If you ALSO want changes entered on B to show up on C you'll need to keep the current B-to-C replicants since even if the A-B replication is setup as bidirectional rows updated on B will not cascade through A to C. Personally, I think that there should be a cascading replication option and I've told Madison that. The problem is, I think, preventing circular replication from eventually looping the update around to update the origin server again. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) IIUG Board of Directors (art@iiug.org) See you at the 2010 IIUG Informix Conference April 25-28, 2010 Overland Park (Kansas City), KS www.iiug.org/conf Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Tue, May 4, 2010 at 11:05 AM, Madison Pruet <mpruet@us.ibm.com> wrote: > You're confusing topology with replication ... ;-) > > You define the endpoints of replication when defining the replicates. = > You > define the topology when defining the servers. > > If you want to replicate from a to [b,c], then you need to define a sin= > gle > replicate with three nodes, not two replicates with two nodes each. > > = > > From: "Georges Martin" <georges_martin_1@hotmail.com> = > > = > > To: ids@iiug.org = > > = > > Date: 05/04/2010 09:56 AM = > > = > > Subject: Enterprise Replication issues [19982] = > > = > > Sent by: ids-bounces@iiug.org = > > = > > Hi, > > IDS version 11.50.FC6 > > OS version: Solaris 10 > > I have 3 servers A, B and C > > A is replicating to B using Enterprise Replication > > B is replicating to C using Enterprise Replication > > >From B to C, I replicate only a subset of tables with a different > structure. > > When I insert a new row in A, it gets correctly replicated to B but the= > > corresponding row does NOTget replicated to C. > > However when I insert a row into B, it gets replicated to C. > > Am I missing something? > > Should I define B twice: once as a secondary for A and one more time as= > a > primary for C? > > Thanks > > _________________________________________________________________ > MSN Dating: Find someone special. Start now. > http://go.microsoft.com/?linkid=3D9729707 > > ***********************************************************************= > ******** > > Forum Note: Use "Reply" to post a response in the discussion forum. > > = > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --00504502cbeffe56aa0485c66988
Correct. Cascading replication is a form of recursion. And just as with recursi= on, if you don't stop the recursion, it will continue forever. = From: "Art Kagel" <art.kagel@gmail.com> = = To: ids@iiug.org = = Date: 05/04/2010 10:43 AM = = Subject: Re: Enterprise Replication issues [19989] = = Sent by: ids-bounces@iiug.org = = To clarify what Madison is saying, there are a couple of points: - ER doesn't cascade. If A replicates a table to B and B replicates tha= t target table as a source to C data updated on A will not replicate to C= . - You have to define a replicant from A to C for each of the subset of tables that you want maintained on C. If you ALSO want changes entered = on B to show up on C you'll need to keep the current B-to-C replicants since= even if the A-B replication is setup as bidirectional rows updated on B will= not cascade through A to C. Personally, I think that there should be a cascading replication option= and I've told Madison that. The problem is, I think, preventing circular replication from eventually looping the update around to update the ori= gin server again. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) IIUG Board of Directors (art@iiug.org) See you at the 2010 IIUG Informix Conference April 25-28, 2010 Overland Park (Kansas City), KS www.iiug.org/conf Disclaimer: Please keep in mind that my own opinions are my own opinion= s and do not reflect on my employer, Advanced DataTools, the IIUG, nor any ot= her organization with which I am associated either explicitly, implicitly, = or by inference. Neither do those opinions reflect those of other individuals= affiliated with any entity with which I am affiliated nor those of the entities themselves. On Tue, May 4, 2010 at 11:05 AM, Madison Pruet <mpruet@us.ibm.com> wrot= e: > You're confusing topology with replication ... ;-) > > You define the endpoints of replication when defining the replicates.= =3D > You > define the topology when defining the servers. > > If you want to replicate from a to [b,c], then you need to define a s= in=3D > gle > replicate with three nodes, not two replicates with two nodes each. > > =3D > > From: "Georges Martin" <georges_martin_1@hotmail.com> =3D > > =3D > > To: ids@iiug.org =3D > > =3D > > Date: 05/04/2010 09:56 AM =3D > > =3D > > Subject: Enterprise Replication issues [19982] =3D > > =3D > > Sent by: ids-bounces@iiug.org =3D > > =3D > > Hi, > > IDS version 11.50.FC6 > > OS version: Solaris 10 > > I have 3 servers A, B and C > > A is replicating to B using Enterprise Replication > > B is replicating to C using Enterprise Replication > > >From B to C, I replicate only a subset of tables with a different > structure. > > When I insert a new row in A, it gets correctly replicated to B but t= he=3D > > corresponding row does NOTget replicated to C. > > However when I insert a row into B, it gets replicated to C. > > Am I missing something? > > Should I define B twice: once as a secondary for A and one more time = as=3D > a > primary for C? > > Thanks > > _________________________________________________________________ > MSN Dating: Find someone special. Start now. > http://go.microsoft.com/?linkid=3D3D9729707 > > *********************************************************************= **=3D > ******** > > Forum Note: Use "Reply" to post a response in the discussion forum. > > =3D > > > > ***********************************************************************= ******** > Forum Note: Use "Reply" to post a response in the discussion forum. > > --00504502cbeffe56aa0485c66988 ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =