RE: perl sybase driver problem

> From: Shane [mailto:swilli40@xxxxxxxxxxx]
> Sent: October 28, 2003 7:11 AM
> 
> Please mail this address, as I probably wont be able to read 
> the mailing list.
> 
> I installed freetds to allow me to connect to a mssql 2000 
> database. The installation went well and all tests passed 
> when i ran 'make check'.
> 
> tsql can succesfully connect to the database and i can run queries.
> 
> the problem:
> i want to use perl DBD::Sybase to connect and run queries, 
> but I keep getting errors. I have installed the latest 
> DBD::Sybase, which didn't work because it was asking for 
> config files. I reverted to 0.91 version of this driver

You're really better off getting the latest of both.  The latest DBD::Sybase
is 1.01.  0.91 hasn't been used since my grandfather sold his horse.  

DBD::Sybase 1.00 with FreeTDS 0.61 (or later) will definitely connect to SQL
Server 2000.  We offer a money-back guarantee on that.  ;-)

> Does this 
> driver use the freetds libs? Does the freetds.conf get used 
> at all when using the sybase driver?

Just to be clear, the layers are:

                        Perl
        uses            DBI
        uses            DBD::Sybase
        uses            "ct-lib" API
implemented by  FreeTDS

DBD::Sybase doesn't communicate directly to the database server; it relies
on a ct-lib implementation, either ours or Sybase's.  

With your connect string, you indicate what server to connect to.
DBD::Sybase passes that information to FreeTDS, which looks it up in
freetds.conf.  

>     -> connect for DBD::Sybase::dr 
> (DBI::dr=HASH(0x4012fbcc)~0x400392e4 'server=RATIONAL_DB' 
> 'clearquest_admin' **** HASH(0x401d5bec)) thr#4001bcd8
> OpenClient message: LAYER = (7) ORIGIN = (2) SEVERITY = (6) 
> NUMBER = (6)
> Message String: ct_con_alloc(): unable to get layer message 
> string: unable to get origin message string: error string not 
> available
> ct_con_alloc failed at 

It looks like you're not connecting.  Could be many things, a TDSDUMP log
would make that clear.  Since you have tsql working, it's probably just a
matter of using the right connect string.  But upgrading the driver would be
good idea in any case.  

HTH.

--jkl


-----------------------------------------
The information contained in this transmission may contain privileged and 
confidential information and is intended only for the use of the person(s) 
named above. If you are not the intended recipient, or an employee or agent 
responsible for delivering this message to the intended recipient, any review, 
dissemination, distribution or duplication of this communication is strictly 
prohibited. If you are not the intended recipient, please contact the sender 
immediately by reply e-mail and destroy all copies of the original message. 
Please note that we do not accept account orders and/or instructions by e-mail, 
and therefore will not be responsible for carrying out such orders and/or 
instructions.