Up Prev Next
From: michael dot x dot peppler at jpmchase dot com
Subject: RE: Sybase upgrade kills DBD 1.04 installation
Date: Dec 20 2007 7:04AM
Could you post perl -V output for a system that works, and one that
Sent by: email@example.com
RE: Sybase upgrade kills DBD 1.04 installation
Rebuild with new open client still fails. We tried this first, but "make
test" fails with the same message for multiple DBD::Sybase versions.
libct.so => /usr/local/sybase/OCS-12_5/lib/libct.so
libcs.so => /usr/local/sybase/OCS-12_5/lib/libcs.so
libtcl.so => /usr/local/sybase/OCS-12_5/lib/libtcl.so
libcomn.so => /usr/local/sybase/OCS-12_5/lib/libcomn.so
libintl.so => /usr/local/sybase/OCS-12_5/lib/libintl.so
libdl.so.1 => /lib/libdl.so.1
libm.so.1 => /lib/libm.so.1
libc.so.1 => /lib/libc.so.1
libsocket.so.1 => /lib/libsocket.so.1
libnsl.so.1 => /lib/libnsl.so.1
libmp.so.2 => /lib/libmp.so.2
sybase/dba/scripts> cat ~/interfaces
master tcp ether drhost 4400
query tcp ether drhost 4400
To reiterate, this works fine on other servers with the same OS, ESD, DBI,
and DBD. The only differences that show up in truss pertain to the
platform, perl version, and maybe LD_LIBRARY_PATH (though no differences
germane to what appears in truss output). The ESD was applied consistent
with the previous two installations. This suggests either the perl build,
or platform specific issues.
Subject: Re: Sybase upgrade kills DBD 1.04 installation
There could be various issues.
First - have you rebuilt DBD::Sybase with the new OpenClient?
Second - if you haven't rebuilt - is the Sybase.so file linked to
libtli.so (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
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 http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.