OpenClient error with Perl DBI Sybase IQ

[cmahajan]

I have another thread on this issue but it seems no one is active on that thread so starting a new one.
Old thread and more details here: DBD::Sybase query execute hangs randomly for Sybase IQ 15.4

I enabled DBI Tracing in my script and here's the error message I got in the trace file. I was lucky enough that the issue occurred shortly after I added the tracing code in my code. From the error message I believe that this is related to the network configuration on my Unix machine (IBM AIX).

Any ideas on how to go about fixing this?

-> FETCH for DBD::Sybase::db (DBI::db=HASH(0x30844064)~INNER 'Driver')
+ ERROR: 50 'OpenClient message: LAYER = (4) ORIGIN = (1) SEVERITY = (
+5) NUMBER = (28) 
Server bhedw_dev, database Message String: ct_results(): protocol spec
+ific layer: external error: There is a tds protocol error. An illegal
+ token was received. OpenClient message: 
LAYER = (1) ORIGIN = (1) SEVERITY = (1) NUMBER = (50) Server bhedw_dev
+, database Message String: ct_cmd_drop(): user api layer: external er
+ror: The connection has been marked dead.

[jfroebe]

Basically the error is Sybase's OpenClient saying we received junk data on the connection to the IQ server. I don't know what to do with it so I'll close the connection.

This isn't a Perl issue. I would open a technical case with SAP/Sybase or ask on the SAP Sybase IQ Community web page.

[mpeppler]

To add to jfroebe's comment - try to use the isql command that is part of your OpenClient package and connect to your IQ server.

If that fails as well then you have a repro that your Sybase IQ techs can work with.

Michael

[Anonymous Monk]

Any ideas on how to go about fixing this?

Lookup the error message in the database(driver) manual or supporting mailing lists, so you know what it means and/or what to do

Then upgrade stuff until it is fixed and/or contact support

For example  [ddg://There is a tds protocol error. An illegal token was received.] There is a tds protocol error. An illegal token was received. -> FIX: SYBASE CT-Library Clients Cannot Connect to Microsoft SQL Server 7.0 says to install a "service pack " on the server, and/or upgrade to newer client libraries

So you'd install new client libraries, then recompile DBD::Sybase to use those new client libraries, and then hopefully the problem goes away