Date: Thu, 8 Oct 1998 06:38:43 +0100 (MET)
From: Carl Karlsson <ckn@findata.se>
To: caldera-users@rim.caldera.com
Subject: Re: glibc-2.0.? and Sybase


On Wed, 7 Oct 1998, Kurt Wall wrote:

> On Wed, Oct 07, 1998 at 06:00:06AM +0100, Carl Karlsson pleaded:
> % 
> % On Tue, 6 Oct 1998, Erik Ratcliffe wrote:
> 
> [snip Sybase support]
> 
> % Anyway, I now know the solutions to 'the hanging client' and 'the failing
> % blk_alloc' problems, if anyone is interested. :)
> 
> Please post the solutions!

OK, in short:

Q: SQL Central / ISQL / other clients just hangs when I connect to the
Linux database. As soon as another client connects, the first one is also
connected immediately. Why?
A: Kernel flaw. Upgrade to 2.0.36 (pre13 currently)

Q: I am trying to use the bulk routines in OpenClient CT-lib. However,
blk_alloc always fails. What's wrong?
A: A localization file called blklib.loc is missing. It can be found in
another OpenClient installation, or from the previous (old) ctlib release
from sybase. I have it installed in $SYBASE/locales/us_english/iso_1/; but
it depends on what locale you're using.
I'd be happy to post my localization file if anyone really needs it.

Q: Is it possible to use raw devices under Linux?
A: No. Might in 2.2 if Sybase supports the new kernel features.

Q: What are the implications from not using raw devices?
A: I haven't the faintest idea, but I would really like to know - from
someone at sybase who knows what (s)he's talking about. Is the Linux
version more insecure in terms of data integrity? It is faster (much
faster) than a database setup using raw devices, but (I have heard) only
for single users. You need raw devices to achieve scalability.


Hope it'll help.. the last two Q's are really things I'd like to have
answered, just threw them in for good measure. :)

Rgds,
  Calle