Article View: borland.public.interbase.replication
Article #709deciphering replication log
From: T.D. Brown
Date: Tue, 09 Oct 2001 18:07
Date: Tue, 09 Oct 2001 18:07
18 lines
1494 bytes
1494 bytes
Below are a few lines from our replication log. There are two consecutive updates to the same table. You'll notice the first update generates a warning that it couldn't find the record to update. So, what did it do with the record? Why wasn't it converted into a insert statement as in the second update? Update 0*383*39*WA Tue Jun 12 14:29:06 2001 WARNING- Record not found - possibly already deleted or Key values modified Update 0*380*39*WA Tue Jun 12 14:29:06 2001 Could not find row to update - Converted to INSERT STATEMENT -- Thank you, Tom Brown Tracker Business Systems, Inc. tom.brown@tbs-inc.net
Technical Details
Message-ID:
<3bc33d53$1_2@dnews>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!newshub2.rdc1.sfba.home.com!news.home.com!feeder.via.net!nntp-relay.ihug.net!newsfeeds.ihug.co.nz!ihug.co.nz!dnewsShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f89d7,edc02467cd2d36ce,start X-Google-Attributes: gidf89d7,public X-Google-ArrivalTime: 2001-10-09 11:19:41 PST From: "T.D. Brown" <tom.brown@tbs-inc.net> Newsgroups: borland.public.interbase.replication Subject: deciphering replication log Date: Tue, 9 Oct 2001 11:07:18 -0700 Lines: 20 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 NNTP-Posting-Host: 206.159.132.34 Message-ID: <3bc33d53$1_2@dnews> X-Trace: dnews 1002650963 206.159.132.34 (9 Oct 2001 11:09:23 -0700) Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!newshub2.rdc1.sfba.home.com!news.home.com!feeder.via.net!nntp-relay.ihug.net!newsfeeds.ihug.co.nz!ihug.co.nz!dnews