On 6/23/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
I suspect that this should really be addressed to a Sybase list.
Sorry about that.
However, what may happen is that the server doesn't have enough network
memory available and therefore is not able to allow the client to connect
with the 16k packet size.
Duh, of course. Just because you configure it, doesn't mean its
physically available.
Ok, until I get a bug fix for the commercial program, I will connect
myself at the new size and if I get an error (and I should), I will do
the step down myself.
Of course, since the number of connections at any time is dynamic, I
could still have problems - I step down to a lower number, meanwhile,
new connections come and now the new number is now too high.
Hmm. Time to spring for some more chips, I guess :-)
Thanks folks.
You should probably take a look at the "additional network memory"
sp_configure option, and read the writeup in Chapter 4 of the System Admin
Guide (page 142 in my 12.5.2 PDF)
Michael
Extranet
[EMAIL PROTECTED] - 23/06/2006 14:36
To: dbi-users
cc:
Subject: DBD::Sybase misleads me?
I have a commercial program that accesses a Sybase 12.5 server. It has
an option to change the packet size of the communucation frame with
the server, but you have to know what size you want.
Sooo, in my perl program, I connect to the database with DBD::Sybase,
execute a
sp_configure 'max network packet size' and then I system() the
commercial program with the argument -zpkt=whatever I got back.
Occasionally, the program responds with
DB-Lib ERROR: 20201: Packet size of 16384 not supported -- size of
13824 used instead. severity is 1
The program then dies, but that is their problem - it should
disconnect and reconnect properly and I will register te bug with them
My question is this what causes this? One minute 16384 is ok and the
next its not. DBD::Sybase is CT-LIb based and their program is DB-Lib
based. Is that a problem?
--
Matthew O. Persico
This message and any attachments (the "message") is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le
"message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
--
Matthew O. Persico
