Re: Very old page bug

"Simmons, Keith" <keith.simmons@office2office.biz> wrote in message news:c3rn0m$c8n$1@terabinaries.xmission.com... > >> > Fourth. Not sure about your dummy statements not being logged. Certainly in > our ER situation we occasionally get records going out of sync and we use a > dummy update to force ER updates to go from one machine to the other. As ER > uses log snooping these updates must be logged. May be a special case with > ER. Nope... 9.40.TC2E1 (I know Windows!...but I can play and write this at the same time! create table t1 (id int) insert into t1 values(1) onmode -l to switch to new logical log < make databases unbuffered logging> update t1 set id=td where 1=1.. 1 row updated Output from onlog to dump the relevant logical log... log uniqid: 5. addr len type xid id link 18 36 CKPOINT 1 5 0 0 1018 44 BEGIN 5 5 0 03/24/2004 21:57:44 28 unknown 1044 60 HUPDAT 5 0 1018 100002 203 0 172 172 1 1080 40 COMMIT 5 0 1044 03/24/2004 21:57:44 2018 36 CKPOINT 1 5 0 0 3018 56 ARCINFO 7 5 0 0 03/24/2004 21:59:02 0xd0ea 5 0x2018 3050 56 ARCINFO 7 0 3018 0 03/24/2004 21:59:02 0xd0ea 5 0x2018 3088 56 ARCINFO 7 0 3050 0 03/24/2004 21:59:02 0xd0ea 5 0x2018 30c0 36 CKPOINT 1 5 0 0 4018 44 BEGIN 7 5 0 03/24/2004 21:59:04 30 unknown 4044 60 HUPDAT 7 0 4018 100002 203 0 172 172 1 4080 40 COMMIT 7 0 4044 03/24/2004 21:59:04 4044.,,HUPDAT... dump of row being logged even though it is a dummy update.. Note this table has NOT had any alters (in-place or otherwise) done on it! ..and ER (and HDR) is not in use!