Michael Peppler
Sybase Consulting
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
Sybase on Linux FAQ
Sybperl FAQ
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: michael dot x dot peppler at jpmchase dot com
Subject: Re: Sybase upgrade kills DBD 1.04 installation
Date: Dec 19 2007 3:39PM

You wrote:

If LD_LIBRARY_PATH is set to the old OCS-12_5/lib directory
(P-EBF11356/DRV.12.5.1), everything is fine again.  Set LD_LIBRARY_PATH
to the new OCS-12_5/lib (P-EBF13138 ESD #12/DRV. and it breaks
DBD::Sybase again (isql, etc are all fine either way).  Two other
servers with Solaris and ESD #12/DRV. work without a problem.

SunOS devhost 5.9 Generic_118558-11 sun4u sparc SUNW,Ultra-Enterprise
(perl, v5.8.0)
SunOS stagehost 5.9 Generic_118558-11 sun4u sparc SUNW,Ultra-80 (perl,

Not Okay:
SunOS drhost 5.9 Generic_118558-11 sun4us sparc FJSV,GPUZC-M (perl,

There could be various issues.

First - have you rebuilt DBD::Sybase with the new OpenClient?

Second - if you haven't rebuilt - is the file linked to (you can use ldd to find that out).

Third - what is the format of the interfaces file entry for the connection 
that fails ? Is it a tli format, or a standard hostname/port ?


This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.

Please refer to for
disclosures relating to UK legal entities.