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.

Duplicate key error on warm standby

3 posts in General Discussion Last posting was on 2011-12-10 01:39:37.0Z
rick_806 Posted on 2011-12-09 17:01:01.0Z
Sender: 13f4.4edcd476.1804289383@sybase.com
From: rick_806
Newsgroups: sybase.public.rep-server
Subject: Duplicate key error on warm standby
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4ee23ecd.416e.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 9 Dec 2011 09:01:01 -0800
X-Trace: forums-1-dub 1323450061 10.22.241.41 (9 Dec 2011 09:01:01 -0800)
X-Original-Trace: 9 Dec 2011 09:01:01 -0800, 10.22.241.41
Lines: 13
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9110
Article PK: 870273

ASE 15.5, Rep Svr 15.2 I am using the generic warm standby
setup, no repdefs. I received a bunch of duplicate key
errors on my replicate server after a crash last night? I am
trying to figure out how this happened.
Would a begin tran with multiple statments (inserts,
updates,e tc.) with a failure of one of the statements yet
user hits commit anyway result in something like this? So
first couple of statements work, one is bad (duplicate key)
and then commit. I don't see these duplicate key errors in
the PDS error log?

Thx,
rick_806


"Mark A. Parsons" <iron_horse Posted on 2011-12-09 20:38:03.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.rep-server
Subject: Re: Duplicate key error on warm standby
References: <4ee23ecd.416e.1681692777@sybase.com>
In-Reply-To: <4ee23ecd.416e.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4ee271ab$1@forums-1-dub>
Date: 9 Dec 2011 12:38:03 -0800
X-Trace: forums-1-dub 1323463083 10.22.241.152 (9 Dec 2011 12:38:03 -0800)
X-Original-Trace: 9 Dec 2011 12:38:03 -0800, vip152.sybase.com
Lines: 24
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9111
Article PK: 870274

Details on what you mean by 'after a crash' ? What crashed and what steps (if any) did you perform to get back up and
running?

Obvious question ... have you verified that nothing (app/user/batch) is making direct modifications against the RDB?

Take a look at case # 10776958 to see if this might match your issue. (Gist of the case is that non-exact numerics -
float/real - may lose some accuracy/precision during replication thus causing a
WS_txn_with_no_repdef_and_therefore_no_PK_definition to look like a new/different record although the PK columns may be
exact; proposed workaround is to define a repdef and PK.)

On 12/09/2011 12:01, rick_806 wrote:
> ASE 15.5, Rep Svr 15.2 I am using the generic warm standby
> setup, no repdefs. I received a bunch of duplicate key
> errors on my replicate server after a crash last night? I am
> trying to figure out how this happened.
> Would a begin tran with multiple statments (inserts,
> updates,e tc.) with a failure of one of the statements yet
> user hits commit anyway result in something like this? So
> first couple of statements work, one is bad (duplicate key)
> and then commit. I don't see these duplicate key errors in
> the PDS error log?
>
> Thx,
> rick_806


rick_806 Posted on 2011-12-10 01:39:37.0Z
Sender: 13f4.4edcd476.1804289383@sybase.com
From: rick_806
Newsgroups: sybase.public.rep-server
Subject: Re: Duplicate key error on warm standby
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4ee2b859.7509.1681692777@sybase.com>
References: <4ee271ab$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 9 Dec 2011 17:39:37 -0800
X-Trace: forums-1-dub 1323481177 10.22.241.41 (9 Dec 2011 17:39:37 -0800)
X-Original-Trace: 9 Dec 2011 17:39:37 -0800, 10.22.241.41
Lines: 38
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9112
Article PK: 870276

Rep Server died making memory request from system, it is
known bug with this version and has happened many times. We
don't do anything other than restart rep server and this
issue surfaced 10 hours after the restart on an oltp db. I
am also thinking the most likely cause is a write to the RDB
which is a DR server and so it is always available.

> Details on what you mean by 'after a crash' ? What
> crashed and what steps (if any) did you perform to get
> back up and running?
>
> Obvious question ... have you verified that nothing
> (app/user/batch) is making direct modifications against
> the RDB?
>
> Take a look at case # 10776958 to see if this might match
> your issue. (Gist of the case is that non-exact numerics
> - float/real - may lose some accuracy/precision during
> replication thus causing a
> WS_txn_with_no_repdef_and_therefore_no_PK_definition to
> look like a new/different record although the PK columns
> may be exact; proposed workaround is to define a repdef
> and PK.)
>
> On 12/09/2011 12:01, rick_806 wrote:
> > ASE 15.5, Rep Svr 15.2 I am using the generic warm
> > standby setup, no repdefs. I received a bunch of
> > duplicate key errors on my replicate server after a
> > crash last night? I am trying to figure out how this
> > happened. Would a begin tran with multiple statments
> > (inserts, updates,e tc.) with a failure of one of the
> > statements yet user hits commit anyway result in
> > something like this? So first couple of statements work,
> > one is bad (duplicate key) and then commit. I don't see
> > these duplicate key errors in the PDS error log?
> >
> > Thx,
> > rick_806