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

4 posts in Replication Last posting was on 2007-03-15 14:45:54.0Z
Paul Man Posted on 2007-03-14 18:14:28.0Z
From: "Paul Man" <paulman@datasoft.ie>
Newsgroups: advantage.Replication
Subject: ignore replication failures
Date: Wed, 14 Mar 2007 18:14:28 -0000
Lines: 13
Organization: DSoft
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: 82.141.233.142
Message-ID: <45f83ab0@solutions.advantagedatabase.com>
X-Trace: 14 Mar 2007 12:10:56 -0700, 82.141.233.142
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!82.141.233.142
Xref: solutions.advantagedatabase.com Advantage.Replication:186
Article PK: 1134043

I have checked the ignore replication failures chaeck box. However what is
happening is that we have a situation where there is a primary key conflict
occurring in certain record insert situations during replication. The
problem is that straight away the whole replication queue is blocked. A
conflict trigger doesn;'t help because it doesn't solve the underlying
problem and I'm not concerned about that. What I am concerned is that with
the ignore replication failures that the whole queue is blocked from
processing just because of one entry failing.

What is the purpose of the "ignore replication failures" check box if it
doesn't ignore problem records?


Peter Funk (ADS) Posted on 2007-03-14 19:16:24.0Z
Date: Wed, 14 Mar 2007 19:16:24 +0000 (UTC)
Message-ID: <864d0bcbace08c9345219f57b17@devzone.advantagedatabase.com>
From: Peter Funk (ADS) <pfunk@nospam.com>
Subject: Re: ignore replication failures
Newsgroups: Advantage.Replication
References: <45f83ab0@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: 14 Mar 2007 13:11:54 -0700, 10.24.38.115
Lines: 38
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.115
Xref: solutions.advantagedatabase.com Advantage.Replication:187
Article PK: 1134045

Hello Paul,
The ignore replication failures option only ignores one kind of failure -
when a replication update modifies any number of records other than one.
So if the update modifies zero records (the target record wasn't found)
or multiple records (the update should only find one record). Any other
type of failures will cause the replication update to stay in the queue and
halt further processing of other updates in the queue.

If you wish to ignore other error codes, you can set the PREMITTED_REP_ERRORS
registry key (or configuration file entry for Linux) and the server will
ignore any error codes you specify. Here's an excerpt from our help file:


Keyword = PERMITTED_REP_ERRORS
This configuration parameter can be used to specify which errors are "allowed"
during replication updates. This is a server-wide setting that affects subscriptions
that have the Ignore Replication Failures option enabled (see Replication
Options). By default, only 7137 errors are permitted and any other errors
that occur will cause replication to the target to be blocked until the replication
update succeeds or is manually removed from the replication queue.

If there are other errors that you want the server to allow during replication
to a target, you can specify them with this configuration setting. Note,
that by customizing the list, it will no longer ignore error 7137 by default.
Therefore, if new error codes are added, you must include 7137 in the list
if you still want to allow that error. The configuration setting is a string
that contains a list of the permitted errors delimited by spaces, commas,
or semicolons. For example:

PERMITTED_REP_ERRORS=7137,7057



Regards,
Peter Funk
Advantage R&D


Paul Man Posted on 2007-03-15 14:22:01.0Z
From: "Paul Man" <paulman@datasoft.ie>
Newsgroups: Advantage.Replication
References: <45f83ab0@solutions.advantagedatabase.com> <864d0bcbace08c9345219f57b17@devzone.advantagedatabase.com>
Subject: Re: ignore replication failures
Date: Thu, 15 Mar 2007 14:22:01 -0000
Lines: 49
Organization: DSoft
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 82.141.233.142
Message-ID: <45f955b5@solutions.advantagedatabase.com>
X-Trace: 15 Mar 2007 08:18:29 -0700, 82.141.233.142
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!82.141.233.142
Xref: solutions.advantagedatabase.com Advantage.Replication:188
Article PK: 1134046

Thanks.

Do the replication records that are problematic still stay in the
replication table or do they simply get ignored and deleted. The issue is
that we still need to identify problematic areas.

"Peter Funk (ADS)" <pfunk@nospam.com> wrote in message
news:864d0bcbace08c9345219f57b17@devzone.advantagedatabase.com...
> Hello Paul,
> The ignore replication failures option only ignores one kind of failure -
> when a replication update modifies any number of records other than one.
> So if the update modifies zero records (the target record wasn't found) or
> multiple records (the update should only find one record). Any other type
> of failures will cause the replication update to stay in the queue and
> halt further processing of other updates in the queue.
>
> If you wish to ignore other error codes, you can set the
> PREMITTED_REP_ERRORS registry key (or configuration file entry for Linux)
> and the server will ignore any error codes you specify. Here's an excerpt
> from our help file:
>
>
> Keyword = PERMITTED_REP_ERRORS
> This configuration parameter can be used to specify which errors are
> "allowed" during replication updates. This is a server-wide setting that
> affects subscriptions that have the Ignore Replication Failures option
> enabled (see Replication Options). By default, only 7137 errors are
> permitted and any other errors that occur will cause replication to the
> target to be blocked until the replication update succeeds or is manually
> removed from the replication queue.
> If there are other errors that you want the server to allow during
> replication to a target, you can specify them with this configuration
> setting. Note, that by customizing the list, it will no longer ignore
> error 7137 by default. Therefore, if new error codes are added, you must
> include 7137 in the list if you still want to allow that error. The
> configuration setting is a string that contains a list of the permitted
> errors delimited by spaces, commas, or semicolons. For example:
>
> PERMITTED_REP_ERRORS=7137,7057
>
>
>
> Regards,
> Peter Funk
> Advantage R&D
>
>


Peter Funk (ADS) Posted on 2007-03-15 14:45:54.0Z
Date: Thu, 15 Mar 2007 14:45:54 +0000 (UTC)
Message-ID: <864d0bcbacf38c934f57a2d2021@devzone.advantagedatabase.com>
From: Peter Funk (ADS) <pfunk@nospam.com>
Subject: Re: ignore replication failures
Newsgroups: Advantage.Replication
References: <45f955b5@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 Mar 2007 08:41:23 -0700, 10.24.38.115
Lines: 7
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.115
Xref: solutions.advantagedatabase.com Advantage.Replication:189
Article PK: 1134047

Updates which return errors that are ignored are removed from the queue.

Regards,
Peter Funk
Advantage R&D