Oninit cdi / Archive
Talk to an expert →

Enterprise replication problem

Posted in 2001

Topics: High Availability & Replication, Data Types & Schema Design, Logging & Checkpoints

Praveen Tummala — — source: Informix-list mailing list archive (1991-1998)

Hi all, I am running enterprise replication between two servers, one in India and one in Belgium. When I delete one replicate and re-create that replicate, I am getting the following messages in the message logs of two servers: messages on India server --------------------------------------- 18:37:14 CDR: encountered invalid varchar in row (ps_name:121:50). 18:37:14 CDR Eval 1: Could not uncompress row 6291591:300 18:37:14 CDR: encountered invalid varchar in row (ps_name:122:50). 18:37:14 CDR Eval 3: Could not uncompress row 6291591:301 18:37:14 CDR: encountered invalid varchar in row (ps_name:101:50). 18:37:14 CDR Eval 2: Could not uncompress row 6291591:303 18:37:52 Fuzzy Checkpoint Completed: duration was 0 seconds,20 buffers not flushed. 18:37:52 Checkpoint loguniq 106, logpos 0x4ce0dc Messages on Belgium server ---------------------------------------- 14:07:41 Checkpoint loguniq 38, logpos 0x8ad0e4 14:07:41 Fuzzy Checkpoint Completed: duration was 1 seconds, 21buffers not flushed. 14:07:13 CDR Eval 2: Could not uncompress row 6291563:304 14:07:13 CDR: encountered invalid varchar in row (ps_name:115:50). 14:07:13 CDR Eval 2: Could not uncompress row 6291563:303 14:07:13 CDR: encountered invalid varchar in row (ps_name:100:50). 14:07:13 CDR Eval 2: Could not uncompress row 6291563:299 14:07:13 CDR: encountered invalid varchar in row (ps_name:116:50). 14:07:13 CDR Eval 2: Could not uncompress row 6291563:299 14:07:13 CDR: encountered invalid varchar in row (ps_name:97:50). 14:07:13 CDR Eval 0: Could not uncompress row 6291563:300 14:07:13 CDR: encountered invalid varchar in row (ps_name:120:50). Any one Know what's the problem is? Thanks, Praveen.

↪ replying to Praveen Tummala
Madison Pruet — — source: Informix-list mailing list archive (1991-1998)

There was a problem with inplace alters and this sounds like that problem. I'd suggest doing the following on both of the servers. begin work without replication; upcate table ..... set <somecol> = <same somecol>; commit work; This will cause the data pages to be converted to the current format. Praveen Tummala wrote: > Hi all, > > I am running enterprise replication between two servers, one in India > and one in Belgium. When I delete one replicate and re-create that > replicate, I am getting the following messages in the message logs of > two servers: > > messages on India server > --------------------------------------- > 18:37:14 CDR: encountered invalid varchar in row (ps_name:121:50). > 18:37:14 CDR Eval 1: Could not uncompress row 6291591:300 > 18:37:14 CDR: encountered invalid varchar in row (ps_name:122:50). > 18:37:14 CDR Eval 3: Could not uncompress row 6291591:301 > 18:37:14 CDR: encountered invalid varchar in row (ps_name:101:50). > 18:37:14 CDR Eval 2: Could not uncompress row 6291591:303 > 18:37:52 Fuzzy Checkpoint Completed: duration was 0 seconds,> 20 buffers not flushed. > 18:37:52 Checkpoint loguniq 106, logpos 0x4ce0dc> > Messages on Belgium server > ---------------------------------------- > 14:07:41 Checkpoint loguniq 38, logpos 0x8ad0e4 > 14:07:41 Fuzzy Checkpoint Completed: duration was 1 seconds, 21> buffers not flushed. > 14:07:13 CDR Eval 2: Could not uncompress row 6291563:304 > 14:07:13 CDR: encountered invalid varchar in row (ps_name:115:50). > 14:07:13 CDR Eval 2: Could not uncompress row 6291563:303 > 14:07:13 CDR: encountered invalid varchar in row (ps_name:100:50). > 14:07:13 CDR Eval 2: Could not uncompress row 6291563:299 > 14:07:13 CDR: encountered invalid varchar in row (ps_name:116:50). > 14:07:13 CDR Eval 2: Could not uncompress row 6291563:299 > 14:07:13 CDR: encountered invalid varchar in row (ps_name:97:50). > 14:07:13 CDR Eval 0: Could not uncompress row 6291563:300 > 14:07:13 CDR: encountered invalid varchar in row (ps_name:120:50).> > Any one Know what's the problem is? > > Thanks, > Praveen.

Glossary