Re: bcp out fails with CTLIB Message: - L5/O1/S5/N18/5/0 when using -A
- From: SybaseNeal <nstack21@xxxxxxxxx>
- Date: Tue, 11 Mar 2008 08:57:25 -0700 (PDT)
Hello,
Were there any errors reported in the ASE error log?
There was a bug fixed in ASE 12.5.3 ESD#6 and higher
where client applications would get the error you reported
but ASE would get a stack trace:
370870 - The message "current process infected with 11" in the module
'kbfalloc' may be reported in the error log when using network packet
size greater than the configured value of "default network packet
size".
There was also a client side bug fixed in bcp 12.5.1 ESD#6 and higher:
368613 - a packetsize larger than 32767 bytes results in an "illegal
length" protocol packet error.
FYI, unless you have changed the maximum transmission unit for your
network,
the packet will be broken up into chunks small enough to fit into the
MTU (usually 1500 bytes).
So setting the packet size to 32768 would allow you the application to
make fewer calls
to read() or write() because they were writing larger chunks but once
the chunk hits the network
layer, it gets fragmented into smaller packets.
So I would be surprised if you were really getting much bang for the
buck by defining
such a large packet size:
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15.0.sag1/html/sag1/sag1231.htm
In fact, you may even be seeing some performance degradation from what
you get with a smaller packet.
Thanks,
Neal
.
- References:
- Prev by Date: Re: Repeat command isql without typing
- Next by Date: ASA unload/reload question
- Previous by thread: bcp out fails with CTLIB Message: - L5/O1/S5/N18/5/0 when using -A
- Next by thread: Re: Example of how to call a stored procedure from C using dblib - needed desperately
- Index(es):
Relevant Pages
|
