Re: HDR question

you are right. I should be able to get the current log id from the syslogs table from primary and secondary server. Thanks for the help. Regards, Miyaki --- Madison Pruet <mpruet@comcast.net> wrote: > But by comparing the difference betwee the current > log id on the primary > with the current log id on the secondary, wouldn't > you get the delta between > the two? > > > ----- Original Message ----- > From: "miyaki" <lcib@yahoo.com> > To: "Madison Pruet" <mpruet@comcast.net>; > <informix-list@iiug.org> > Sent: Monday, September 27, 2004 10:30 PM > Subject: Re: HDR question > > > > The current log id in primary will be exactly the > same > > as the log id in secondary provided that the > > replication is in fully functional operation. > > > > However, in order to fully restore the > replication, > > the secondary server has to roll forwards with the > > logs from primary server until it catch up the > current > > log id in primary server. During the roll forwards > > process (some called as replication recovery > process), > > I need to know how many logs have not been > replicated > > or roll forward in secondary servers. > > > > My objective is to have a process to constant > > monitoring the logs and to ensure they are > replicated > > to secondary servers before the logs are being > reuse > > in primary server. > > > > I did encountered a problem where the primary > database > > engine is halted due to the logical logs are not > freed > > as they have not been replicated to secondary > server > > due to network slowness issue. > > > > If I can find the info from the SMI tables instead > of > > using the onstat -g dri command, then it would > help me > > to reinforce the logic in my monitoring utility. > > > > So, my quention is there any SMI tables that keep > > track of the last replicated log id? > > > > Thanks & regards, > > Miyaki > > > > --- Madison Pruet <mpruet@comcast.net> wrote: > > > > > Since the logs on the secondary are copied from > the > > > primary, wouldn't that > > > be the current log position on the secondary? > > > > > > > > > "miyaki" <lcib@yahoo.com> wrote in message > > > news:cipnd0$hon$1@news.xmission.com... > > > > > > > > Hi all, > > > > > > > > Is there anyone know which SMI table keep > track of > > > the > > > > Last DR CKPT info? sysdri tables from > sysmaster > > > > database doesn't contains the info. I need to > know > > > > what is the current log id that being > replicated > > > to > > > > the secondary server. > > > > > > > > Informix Dynamic Server Version 7.31.UC2 -- > > > On-Line > > > > (Prim) -- Up 6 days 09:13:16 -- 258864 Kbytes > > > > > > > > Data Replication: > > > > Type State Paired server > > > Last > > > > DR CKPT (id/pg) > > > > primary off boston > > > > 23904 / 120 > > > > > > > > DRINTERVAL 15 > > > > DRTIMEOUT 60 > > > > DRAUTO 0 > > > > DRLOSTFOUND /usr/informix/etc/dr.lostfound> > > > > > > > Thanks & regards, > > > > Miyaki > > > > > > > > > > > > > > > > __________________________________ > > > > Do you Yahoo!? > > > > New and Improved Yahoo! Mail - Send 10MB > messages! > > > > http://promotions.yahoo.com/new_mail > > > > sending to informix-list > > > > > > > > > > > > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam > protection around > > http://mail.yahoo.com > > __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail sending to informix-list

I know extactly what you are trying to achieve within script. repaytab in syscdr contain current logid only. I do not know for sure about table in question,however, I can think of the following work around (assuming Unix OS): 1. Use onstat -g ddr (see output below) 2. Check Snoopy, Repay and Current IDs 3. Use print, awk etc. to check Replay ID Replay ID will tell us about the logs to be replicated or has been replicated to secondary. ----------------------------------------------------------------------- IBM Informix Dynamic Server Version 9.40.UC3 -- On-Line -- ..... DDR -- Running -- # Event Snoopy Snoopy Replay Replay Current Current Buffers ID Position ID Position ID Position 1552 10511 11ff278 10511 d4940c 10511 1218000 Log Pages Snooped: From From Tossed Cache Disk (LBC full) 485409 414 0 Total dynamic log requests: 0 DDR events queue Type TX id Partnum Row id ------------------------------------------------------------------------- Hari