Re: Replication question

Laurie Gustin wrote:
Hmmm - the replay position hasnt been overwritten. I have attached onstat -l and onstat -g ddr outputs.

I added a bunch of logs last night to make sure we didnt block again until I could do more research this morning (and think more clearly..)
as you can see from the onstat -l output, there are tons of new logs out there, but the system just dynamically created log #89. That really confused me.

so maybe the problem is just with my logs...

onstat -g stk of the ddr thread?



Thanks.
Laurie

<jprenaut@xxxxxxxxx> 11/21/07 10:38 AM >>>

My question has to do with the onstat -g ddr output (see below..) just what is the value under Tossed (LBC full) Im thinking that is all my data that is just being tossed and not replicating. Also the snoopy and replay position are not moving at all...


The value under Tossed is that as your current system is generating
log records and putting them in the logical log buffer, when the
logical log buffer is getting flushed to disk, CDR will attempt to
copy that logical log buffer from memory into a cdr specific log
record buffer cache for the snoopy thread so it wouldn't have to read
those records from disk. However, there is a limited amount of those
buffers and if that cache is already full, then we increment the
tossed count and then those records would just have to be snooped from
disk. I don't believe that would be a reason why stuff isn't
replicating. It looks to be more of a performance sort of value where
ideally the snooper would be running more quickly if it was able to
get it's work from this cache and not have to retrieve it from disk.

Did the replay postion get over written? When the server was bounced
was there any messages in the online.log concerning the ability of CDR
to start backup? If logical log id 38464 (uniqid from onstat -l
output) is no longer on disk (ie the reply position getting over
written), then yeah CDR is in big trouble, as that would be the spot
at which the snoopy thread needs to get to start back up snooping the
logs, and if it can't then I don't believe anything will get
replicated since the snooper isn't reading any log records. However,
if logical log id 38464 is still on disk and the replay position
hasn't been over written, without seeing other information it would be
hard to say why the replay position isn't advancing.

Jacques
IBM Informix
_______________________________________________
Informix-list mailing list
Informix-list@xxxxxxxx http://www.iiug.org/mailman/listinfo/informix-list


.

Relevant Pages

  • Re: Replication question
    ... How do I know which CDR thread? ... I did onstat -g stk all and just deleted all but the CDR stuff ... logical log buffer is getting flushed to disk, ... those records from disk. ...
    (comp.databases.informix)
  • Re: Replication question
    ... logical log buffer is getting flushed to disk, CDR will attempt to ... those records from disk. ... hard to say why the replay position isn't advancing. ...
    (comp.databases.informix)
  • Re: DVD copy
    ... So now I have this .cdr copy, but it doesn't play. ... By using disk utility and making a new image. ... MPeg StreamClip also produces myriad formats ...
    (comp.sys.mac.apps)
  • Free sapce on CDR
    ... I have a mini CD capacity. ... This is the over reported CDR capacity (the CD has 185 MB written on ... Disk sub type: Medium Type B, ... Manufacturer: Lead Data Inc. ...
    (comp.os.linux.misc)
  • Re: XP does not reconize my burner in properties
    ... No luck. ... But it does say it's a CDR now. ... I place a blank disk in a disk, ... > notepad. ...
    (alt.os.windows-xp)