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.

Replication issues are difficult to find.

6 posts in Replication Last posting was on 2011-03-02 09:01:42.0Z
mike grace Posted on 2011-02-08 10:35:53.0Z
Date: Tue, 8 Feb 2011 10:35:53 +0000 (UTC)
Message-ID: <b9f6cef8f3ea8cd9593186c7f2f@devzone.advantagedatabase.com>
From: mike grace <mikeg@computastat-group.co.uk>
Subject: Replication issues are difficult to find.
Newsgroups: Advantage.Replication
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=iso-8859-1; format=flowed
X-Newsreader: JetBrains Omea Reader 1098.1
NNTP-Posting-Host: 188.220.18.141
X-Trace: 8 Feb 2011 02:35:31 -0800, 188.220.18.141
Lines: 13
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Replication:436
Article PK: 1134288

Hi,

Could the reason why a record won't replicate be put into the replication
queue (another field) and not into the error log.

When replication gets stuck, it is very difficult to figure out why.

Regards


Mike


Mark Wilkins Posted on 2011-02-09 20:01:46.0Z
From: "Mark Wilkins" <a@b.c>
Newsgroups: Advantage.Replication
References: <b9f6cef8f3ea8cd9593186c7f2f@devzone.advantagedatabase.com>
In-Reply-To: <b9f6cef8f3ea8cd9593186c7f2f@devzone.advantagedatabase.com>
Subject: Re: Replication issues are difficult to find.
Date: Wed, 9 Feb 2011 13:01:46 -0700
Lines: 1
Organization: Sybase
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
NNTP-Posting-Host: 10.6.199.122
Message-ID: <4d52f28f$1@solutions.advantagedatabase.com>
X-Trace: 9 Feb 2011 12:01:19 -0800, 10.6.199.122
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Replication:440
Article PK: 1134292

Hi Mike,

That's a very good idea. I will make an entry to investigate that.

Mark Wilkins
Advantage R&D

"mike grace" <mikeg@computastat-group.co.uk> wrote in message
news:b9f6cef8f3ea8cd9593186c7f2f@devzone.advantagedatabase.com...
> Hi,
>
> Could the reason why a record won't replicate be put into the replication
> queue (another field) and not into the error log.
>
> When replication gets stuck, it is very difficult to figure out why.
>
> Regards
>
>
> Mike
>
>


mike grace Posted on 2011-02-10 09:31:10.0Z
Date: Thu, 10 Feb 2011 09:31:10 +0000 (UTC)
Message-ID: <b9f6cef8f4978cd971c62ce9392@devzone.advantagedatabase.com>
From: mike grace <mikeg@computastat-group.co.uk>
Subject: Re: Replication issues are difficult to find.
Newsgroups: Advantage.Replication
References: <4d52f28f$1@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 Reader 1098.1
NNTP-Posting-Host: 188.220.18.141
X-Trace: 10 Feb 2011 01:30:44 -0800, 188.220.18.141
Lines: 32
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Replication:442
Article PK: 1134295

Hello Mark,

Thank you.


Regards


Mike

> Hi Mike,
>
> That's a very good idea. I will make an entry to investigate that.
>
> Mark Wilkins
> Advantage R&D
> "mike grace" <mikeg@computastat-group.co.uk> wrote in message
> news:b9f6cef8f3ea8cd9593186c7f2f@devzone.advantagedatabase.com...
>
>> Hi,
>>
>> Could the reason why a record won't replicate be put into the
>> replication queue (another field) and not into the error log.
>>
>> When replication gets stuck, it is very difficult to figure out why.
>>
>> Regards
>>
>> Mike
>>


Nick Friend Posted on 2011-02-10 17:37:00.0Z
From: "Nick Friend" <jnk@tekhne.biz>
Newsgroups: Advantage.Replication
References: <b9f6cef8f3ea8cd9593186c7f2f@devzone.advantagedatabase.com>
In-Reply-To: <b9f6cef8f3ea8cd9593186c7f2f@devzone.advantagedatabase.com>
Subject: Re: Replication issues are difficult to find.
Date: Thu, 10 Feb 2011 17:37:00 -0000
Lines: 20
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6001.18416
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18483
X-Antivirus: avast! (VPS 110210-0, 10/02/2011), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: 86.138.189.150
Message-ID: <4d542227$1@solutions.advantagedatabase.com>
X-Trace: 10 Feb 2011 09:36:39 -0800, 86.138.189.150
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Replication:443
Article PK: 1134296

Excellent idea.... I'll second that.

Nick

"mike grace" <mikeg@computastat-group.co.uk> wrote in message
news:b9f6cef8f3ea8cd9593186c7f2f@devzone.advantagedatabase.com...
> Hi,
>
> Could the reason why a record won't replicate be put into the replication
> queue (another field) and not into the error log.
>
> When replication gets stuck, it is very difficult to figure out why.
>
> Regards
>
>
> Mike
>
>


Mark Wilkins Posted on 2011-03-01 15:38:00.0Z
From: "Mark Wilkins" <a@b.c>
Newsgroups: Advantage.Replication
References: <b9f6cef8f3ea8cd9593186c7f2f@devzone.advantagedatabase.com>
In-Reply-To: <b9f6cef8f3ea8cd9593186c7f2f@devzone.advantagedatabase.com>
Subject: Re: Replication issues are difficult to find.
Date: Tue, 1 Mar 2011 08:38:00 -0700
Lines: 1
Organization: Sybase
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
NNTP-Posting-Host: 10.6.199.122
Message-ID: <4d6d12d7$1@solutions.advantagedatabase.com>
X-Trace: 1 Mar 2011 07:37:59 -0800, 10.6.199.122
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Replication:444
Article PK: 1134297

Hi,

We have made an update that will hopefully help with this. We added three
fields to the replication table for the error code, the error text (e.g.,
SQL error information), and the SQL statement. It is the same information
that appears in the error log but will be in the top-most entry of the queue
when a failure occurs. This update will be in the next v10.1 update (coming
in the next month or two I believe).

Thanks for suggesting this improvement.

Mark Wilkins
Advantage R&D

"mike grace" <mikeg@computastat-group.co.uk> wrote in message
news:b9f6cef8f3ea8cd9593186c7f2f@devzone.advantagedatabase.com...
> Hi,
>
> Could the reason why a record won't replicate be put into the replication
> queue (another field) and not into the error log.
>
> When replication gets stuck, it is very difficult to figure out why.
>
> Regards
>
>
> Mike
>
>


mike grace Posted on 2011-03-02 09:01:42.0Z
Date: Wed, 2 Mar 2011 09:01:42 +0000 (UTC)
Message-ID: <b9f6cef8f7448cda6cf9563de97@devzone.advantagedatabase.com>
From: mike grace <mikeg@computastat-group.co.uk>
Subject: Re: Replication issues are difficult to find.
Newsgroups: Advantage.Replication
References: <4d6d12d7$1@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 Reader 1098.1
NNTP-Posting-Host: 188.220.18.141
X-Trace: 2 Mar 2011 01:01:40 -0800, 188.220.18.141
Lines: 39
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.Replication:445
Article PK: 1134298

Hello Mark,

Thats excellent news.

Regards


Mike

> Hi,
>
> We have made an update that will hopefully help with this. We added
> three fields to the replication table for the error code, the error
> text (e.g., SQL error information), and the SQL statement. It is the
> same information that appears in the error log but will be in the
> top-most entry of the queue when a failure occurs. This update will
> be in the next v10.1 update (coming in the next month or two I
> believe).
>
> Thanks for suggesting this improvement.
>
> Mark Wilkins
> Advantage R&D
> "mike grace" <mikeg@computastat-group.co.uk> wrote in message
> news:b9f6cef8f3ea8cd9593186c7f2f@devzone.advantagedatabase.com...
>
>> Hi,
>>
>> Could the reason why a record won't replicate be put into the
>> replication queue (another field) and not into the error log.
>>
>> When replication gets stuck, it is very difficult to figure out why.
>>
>> Regards
>>
>> Mike
>>