Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Detecting replication not processing

6 posts in Replication Last posting was on 2007-02-22 12:05:25.0Z
Paul Man Posted on 2007-02-15 12:42:25.0Z
From: "Paul Man" <paulman@datasoft.ie>
Newsgroups: advantage.Replication
Subject: Detecting replication not processing
Date: Thu, 15 Feb 2007 12:42:25 -0000
Lines: 15
Organization: DSoft
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
NNTP-Posting-Host: 82.141.233.142
Message-ID: <45d4545c@solutions.advantagedatabase.com>
X-Trace: 15 Feb 2007 05:38:52 -0700, 82.141.233.142
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!82.141.233.142
Xref: solutions.advantagedatabase.com Advantage.Replication:170
Article PK: 1134026

What would the best option be to detect where replication is not operational
due to remote connectin being down for example.
In this scenario, say that the remote link went down but became available
after a while but that replication hasn't restarted. Obviously we would
want to process the replication queue ASAP so if there was some sort of
indication that we could query e.g. the earliest time a replication update
is still in the queue for a particular remote database. We could then queyr
the replication table for this and determine if a time is > 10 minutes for
example.

Otherwise is there a setting to force the replication to retry failed
updates every minute instead of the default method where the retries get
more infrequent each time.


Lance Schmidt Posted on 2007-02-15 16:30:15.0Z
From: "Lance Schmidt" <LanceSc@ExtendSys.com>
Newsgroups: advantage.Replication
References: <45d4545c@solutions.advantagedatabase.com>
Subject: Re: Detecting replication not processing
Date: Thu, 15 Feb 2007 09:30:15 -0700
Lines: 27
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
NNTP-Posting-Host: 10.24.38.197
Message-ID: <45d4898f@solutions.advantagedatabase.com>
X-Trace: 15 Feb 2007 09:25:51 -0700, 10.24.38.197
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.197
Xref: solutions.advantagedatabase.com Advantage.Replication:171
Article PK: 1134029

Hi Paul,

Thanks for the bug report this will be fixed in the next service release.

Best Regards,

Lance Schmidt
Advantage R&D

"Paul Man" <paulman@datasoft.ie> wrote in message
news:45d4545c@solutions.advantagedatabase.com...
> What would the best option be to detect where replication is not
> operational due to remote connectin being down for example.
> In this scenario, say that the remote link went down but became available
> after a while but that replication hasn't restarted. Obviously we would
> want to process the replication queue ASAP so if there was some sort of
> indication that we could query e.g. the earliest time a replication update
> is still in the queue for a particular remote database. We could then
> queyr the replication table for this and determine if a time is > 10
> minutes for example.
>
> Otherwise is there a setting to force the replication to retry failed
> updates every minute instead of the default method where the retries get
> more infrequent each time.
>


Lance Schmidt Posted on 2007-02-15 16:36:51.0Z
From: "Lance Schmidt" <LanceSc@ExtendSys.com>
Newsgroups: advantage.Replication
References: <45d4545c@solutions.advantagedatabase.com> <45d4898f@solutions.advantagedatabase.com>
Subject: Re: Detecting replication not processing
Date: Thu, 15 Feb 2007 09:36:51 -0700
Lines: 39
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
NNTP-Posting-Host: 10.24.38.197
Message-ID: <45d48b1a@solutions.advantagedatabase.com>
X-Trace: 15 Feb 2007 09:32:26 -0700, 10.24.38.197
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.197
Xref: solutions.advantagedatabase.com Advantage.Replication:173
Article PK: 1134031

Sorry Paul,

Not enough coffee this morning. I meant to reply to your ARC bug post.`

Best Regards,

Lance Schmidt
Advantage R&D

"Lance Schmidt" <LanceSc@ExtendSys.com> wrote in message
news:45d4898f@solutions.advantagedatabase.com...
> Hi Paul,
>
> Thanks for the bug report this will be fixed in the next service release.
>
> Best Regards,
>
> Lance Schmidt
> Advantage R&D
>
> "Paul Man" <paulman@datasoft.ie> wrote in message
> news:45d4545c@solutions.advantagedatabase.com...
>> What would the best option be to detect where replication is not
>> operational due to remote connectin being down for example.
>> In this scenario, say that the remote link went down but became available
>> after a while but that replication hasn't restarted. Obviously we would
>> want to process the replication queue ASAP so if there was some sort of
>> indication that we could query e.g. the earliest time a replication
>> update is still in the queue for a particular remote database. We could
>> then queyr the replication table for this and determine if a time is >
>> 10 minutes for example.
>>
>> Otherwise is there a setting to force the replication to retry failed
>> updates every minute instead of the default method where the retries get
>> more infrequent each time.
>>
>
>


Peter Funk (ADS) Posted on 2007-02-15 16:33:01.0Z
Date: Thu, 15 Feb 2007 16:33:01 +0000 (UTC)
Message-ID: <864d0bcba90d8c91efb6b7fe0f9@devzone.advantagedatabase.com>
From: Peter Funk (ADS) <pfunk@nospam.com>
Subject: Re: Detecting replication not processing
Newsgroups: Advantage.Replication
References: <45d4545c@solutions.advantagedatabase.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=iso-8859-1; format=flowed
X-Newsreader: JetBrains Omea Pro 1098.1
NNTP-Posting-Host: 10.24.38.115
X-Trace: 15 Feb 2007 09:28:36 -0700, 10.24.38.115
Lines: 23
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.115
Xref: solutions.advantagedatabase.com Advantage.Replication:172
Article PK: 1134030

Hello Paul,
Replication updates which are waiting to be processed (for whatever reason)
are stored in the replication queue. The replication queue is just a table
in the dictionary. By default the queue's table name is the subscription
name with "__" appended to the front. To see if any replication updates
are pending, you could query the table to see if it has any records. For
example:

SELECT COUNT(*) FROM __subscription;

If the count is non zero, you'd know there are pending updates. You could
then use the sp_ProcessReplicationQueues() system procedure to force Advantage
to attempt to process the replication updates in the queue. If you wanted
to know why the replication update failed, you could query the error log
on the server looking for specific replication errors. This might be helpful
in deciding if you wanted to use the sp_ProcessReplicationQueues() procedure
at that time.

Regards,
Peter Funk
Advantage R&D


Paul Man Posted on 2007-02-20 16:08:44.0Z
From: "Paul Man" <paulman@datasoft.ie>
Newsgroups: Advantage.Replication
References: <45d4545c@solutions.advantagedatabase.com> <864d0bcba90d8c91efb6b7fe0f9@devzone.advantagedatabase.com>
Subject: Re: Detecting replication not processing
Date: Tue, 20 Feb 2007 16:08:44 -0000
Lines: 32
Organization: DSoft
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
NNTP-Posting-Host: 82.141.233.142
Message-ID: <45db1c41@solutions.advantagedatabase.com>
X-Trace: 20 Feb 2007 09:05:21 -0700, 82.141.233.142
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!82.141.233.142
Xref: solutions.advantagedatabase.com Advantage.Replication:179
Article PK: 1134037

I noticed that but at the time of query there could be replication records
just after being entered. I must check to see if those tables contain a a
replication date/time as that owuld give a problem indication if the time
was too long.

"Peter Funk (ADS)" <pfunk@nospam.com> wrote in message
news:864d0bcba90d8c91efb6b7fe0f9@devzone.advantagedatabase.com...
> Hello Paul,
> Replication updates which are waiting to be processed (for whatever
> reason) are stored in the replication queue. The replication queue is
> just a table in the dictionary. By default the queue's table name is the
> subscription name with "__" appended to the front. To see if any
> replication updates are pending, you could query the table to see if it
> has any records. For example:
>
> SELECT COUNT(*) FROM __subscription;
>
> If the count is non zero, you'd know there are pending updates. You could
> then use the sp_ProcessReplicationQueues() system procedure to force
> Advantage to attempt to process the replication updates in the queue. If
> you wanted to know why the replication update failed, you could query the
> error log on the server looking for specific replication errors. This
> might be helpful in deciding if you wanted to use the
> sp_ProcessReplicationQueues() procedure at that time.
>
> Regards,
> Peter Funk
> Advantage R&D
>
>


Joachim Duerr (ADS) Posted on 2007-02-22 12:05:25.0Z
From: "Joachim Duerr (ADS)" <jojo.duerr@gmx.de>
Subject: Re: Detecting replication not processing
Newsgroups: Advantage.Replication
References: <45d4545c@solutions.advantagedatabase.com> <864d0bcba90d8c91efb6b7fe0f9@devzone.advantagedatabase.com> <45db1c41@solutions.advantagedatabase.com>
Organization: iAnywhere
User-Agent: XanaNews/1.18.1.2
X-Face: ,QMv7[luB)BpWAQ~:"kw6n%0ieY63.:g2K3n~8ky0;||5Xle*Xq+=~<Fy:0CVC2nx@8~vZ
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
NNTP-Posting-Host: 130.214.79.11
Message-ID: <45dd8705@solutions.advantagedatabase.com>
Date: 22 Feb 2007 05:05:25 -0700
X-Trace: 22 Feb 2007 05:05:25 -0700, 130.214.79.11
Lines: 26
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!130.214.79.11
Xref: solutions.advantagedatabase.com Advantage.Replication:183
Article PK: 1134041


Paul Man wrote in <45db1c41@solutions.advantagedatabase.com>:

> I noticed that but at the time of query there could be replication
> records just after being entered. I must check to see if those tables
> contain a a replication date/time as that owuld give a problem
> indication if the time was too long.

you could try with a trigger. This one checks on every insert for the
records older than 10 minutes:

CREATE TRIGGER trig_ins ON [__subscription_name]
AFTER INSERT
BEGIN
declare cnt integer;
cnt=(select count(*) from __subscription_name where
timestampdiff(SQL_TSI_MINUTE, updatetime, now())>=10);
if cnt>0 then
EXECUTE PROCEDURE sp_ProcessReplicationQueues(1);
end if;
END;

--
Joachim Duerr
System Consultant (Advantage Database Server)
Sybase iAnywhere
advantagesupport[AT]ianywhere.com