Re: ER question

Before you took machine B down for maintenance work, did you stopped the replication or suspended it ? When you stop the replication, ER does not capture data where as if you suspend replication, then data will get captured and won't be sent until you resume replication. HTH, Nilesh. informix-list-bounces@iiug.org wrote on 03/10/2008 04:46:48 AM: > IDS 7.31 > > We have set up ER between two servers with update anywhere scenario. > The select condition is "select * " with no filtering. > > We notice that during the weekend when we take a machine down for > maintenance work, after it comes back up, very frequently the replicated > tables go out of sync. Upon investigation I found that the rows which are > missing on machine B (which was taken down) existed on Machine A > with NULL values in cdrtime. As I understand, a null cdrtime indicates > that the rows existed prior to the definition of the replicates, or the row > was inserted in "BEGIN WORK WITHOUT REPLICATION". I am trying > to find out how the row got created on machine A with null cdrtime. that > explains why the row was never propagated to machine B after it was > back up. > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list

Nilesh Ozarkar wrote: > Before you took machine B down for maintenance work, did you stopped the > replication or suspended it ? > > When you stop the replication, ER does not capture data where as if you > suspend replication, > then data will get captured and won't be sent until you resume replication. > > HTH, > Nilesh. > > <snip> Incorrect, or, perhaps, even worse, incomplete. If you do a "cdr stop" then ER will store where is has snooped up to (i.e. Logical Log ID and Logical Log Position). If you then do a "cdr start" then ER will carry on where it left off (i.e. at the stored Logical Log ID and Logical Log Pos). The main worry about doing a "cdr stop" is that the logical logs will wrap around past the stored LLID / LLPOS. This differs from a "cdr stop repl repl_name" where the data is no longer captured for the "stopped" replicate. This is when "cdr suspend replicate repl_name". :S