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.

Line is too long--help

2 posts in General Discussion (old) Last posting was on 2010-06-01 19:32:27.0Z
islam@sybaseNews Posted on 2010-05-29 08:10:52.0Z
From: "islam@sybaseNews" <islam@alsawan.com>
Newsgroups: sybase.public.sqlanywhere
Subject: Line is too long--help
Lines: 14
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4c00cc0c@forums-1-dub>
Date: 29 May 2010 01:10:52 -0700
X-Trace: forums-1-dub 1275120652 10.22.241.152 (29 May 2010 01:10:52 -0700)
X-Original-Trace: 29 May 2010 01:10:52 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sqlanywhere:354
Article PK: 866774

I have sybase SQL Anywhere V9.0.2.3924, I am using replication between our
bracnhes. few weeks I have received the following error message: Line is too
long, buffer overflow. I have checked the sybase website and found that I
have to add -l 15k to the dbremote option. I have followed the instruction
in the following link:
http://search.sybase.com/kbx/solvedcases?id_number=41002907
and re-extracting the database, restarting the replication, but still
getting the same error.

Any suggestion?


"Nick Elson [Sybase iAnywhere]" < Posted on 2010-06-01 19:32:27.0Z
From: "Nick Elson [Sybase iAnywhere]" <@nick@dot@elson@at@sybase@dot@com@>
Newsgroups: sybase.public.sqlanywhere
References: <4c00cc0c@forums-1-dub>
In-Reply-To: <4c00cc0c@forums-1-dub>
Subject: Re: Line is too long--help
Lines: 41
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.6002.18197
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18197
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4c05604b$1@forums-1-dub>
Date: 1 Jun 2010 12:32:27 -0700
X-Trace: forums-1-dub 1275420747 10.22.241.152 (1 Jun 2010 12:32:27 -0700)
X-Original-Trace: 1 Jun 2010 12:32:27 -0700, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sqlanywhere:355
Article PK: 866772

Are you using SMTP or some other email technology? If so
then setting the -l to the limitation of that server could be a
solution; as it was way back when in V5.5 (when case#
41002907 was current).

I do not quite understand how adding that -L setting affects this but ...
if you are going to adjust that, make sure it is set on the sending side
and that both sides match.

In the support case you noted (or at least one I was involved with
back then) we had to keep adjusting down the the -l setting until
it started to work for the specific SMTP server in use. In another
similar case the customer changed the SMTP software because it
was too restrictive.

If none of this helps try setting up the debug option via the
set remote <> option debug='yes'

and run dbremote with the -v -o switches.


Best of luck.

"islam@sybaseNews" <islam@alsawan.com> wrote in message
news:4c00cc0c@forums-1-dub...
>I have sybase SQL Anywhere V9.0.2.3924, I am using replication between our
>bracnhes. few weeks I have received the following error message: Line is
>too long, buffer overflow. I have checked the sybase website and found that
>I have to add -l 15k to the dbremote option. I have followed the
>instruction in the following link:
>http://search.sybase.com/kbx/solvedcases?id_number=41002907
> and re-extracting the database, restarting the replication, but still
> getting the same error.
>
> Any suggestion?
>
>
>
>