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.

Ignore Replication Failures

2 posts in Replication Last posting was on 2006-05-08 19:22:47.0Z
Simon Stanley Posted on 2006-05-08 18:54:14.0Z
From: "Simon Stanley" <sstanley@astecinc.com>
Newsgroups: advantage.Replication
Subject: Ignore Replication Failures
Date: Mon, 8 May 2006 14:54:14 -0400
Lines: 17
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1506
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
NNTP-Posting-Host: 12.177.82.200
Message-ID: <445f933d@solutions.advantagedatabase.com>
X-Trace: 8 May 2006 12:51:41 -0700, 12.177.82.200
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!12.177.82.200
Xref: solutions.advantagedatabase.com Advantage.Replication:121
Article PK: 1133979

I would like to be able to specify that 7057 errors (Key Violation) be
ignored in addition to the 7137 errors (Unexpected number of records
updated) that are currently ignored by selecting the Ignore Replication
Failures option.

In our application a user of the target database may need to insert a record
when the connection is down. This currently causes the replication queue to
be blocked when the connection is restored and the same record has been
inserted into the source database while the connection was down.

Any thoughts/suggestions?

Regards,

Simon Stanley


Mark Wilkins Posted on 2006-05-08 19:22:47.0Z
From: "Mark Wilkins" <tired@of.spam>
Newsgroups: advantage.Replication
References: <445f933d@solutions.advantagedatabase.com>
Subject: Re: Ignore Replication Failures
Date: Mon, 8 May 2006 13:22:47 -0600
Lines: 35
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: 198.102.102.13
Message-ID: <445f99b7@solutions.advantagedatabase.com>
X-Trace: 8 May 2006 13:19:19 -0700, 198.102.102.13
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!198.102.102.13
Xref: solutions.advantagedatabase.com Advantage.Replication:122
Article PK: 1133980

Hi Simon,

I will add an item to the customer suggestion list for this. What we
probably need is way for the developer to be able to specify a set of errors
to ignore. It would allow much greater control over that type of situation.

In the near term, though, I do have any suggestions. I do not think there
is any way to make Advantage ignore that error condition.

Mark Wilkins
Advantage R&D

"Simon Stanley" <sstanley@astecinc.com> wrote in message
news:445f933d@solutions.advantagedatabase.com...
>I would like to be able to specify that 7057 errors (Key Violation) be
> ignored in addition to the 7137 errors (Unexpected number of records
> updated) that are currently ignored by selecting the Ignore Replication
> Failures option.
>
> In our application a user of the target database may need to insert a
> record
> when the connection is down. This currently causes the replication queue
> to
> be blocked when the connection is restored and the same record has been
> inserted into the source database while the connection was down.
>
> Any thoughts/suggestions?
>
> Regards,
>
> Simon Stanley
>
>