DBD Oracle module
am 13.11.2006 18:37:59 von shannon.kerr------_=_NextPart_001_01C7074A.768AE11E
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Hello,
I'm sorry to bother you, but I saw Dave Moellenhoff's name and email in
the DBD::Oracle README.help.txt fie for an issue similar to what our
team is seeing when using DBD::Oracle 1.19 that our computing team
installed for our development team. I tried contacting him at the
provided email address with no success (is he the same Dave Moellenhoff
that is the CTO for Salesforce.com?). Our local computing team seems to
not be able to resolve a library path issue we are seeing when using
DBD::Oracle. I think what they're asking us and our customers to do is
a work-around and not the way things should be. Here is the error we
are seeing when we use our "ftrq" tool which uses DBD Oracle:
=20
(SunOS 5.6)
=20
$ ftrq
install_driver(Oracle) failed: Can't load
'/apps/public/lib/perlmodules/5.8.4/sun4-solaris/auto/DBD/Or acle/Oracle.
so' for module DBD::Oracle: ld.so.1: /apps/public/bin/perl: fatal:
libclntsh.so.9.0: open failed: No such file or directory at
/apps/public/perl_5.8.4/lib/5.8.4/sun4-solaris/DynaLoader.pm line 230.
at (eval 3) line 3
Compilation failed in require at (eval 3) line 3.
Perhaps a required shared library or dll isn't installed where expected
at /mot/proj/ddts/admin/lib/Oracle.pm line 137
The work around is to set the following:
LD_LIBRARY_PATH=3D/apps/vendor/oracle/lib
After setting this the execution is fine. I see this comment in the
README.help.txt file from Mr. Moellenhoff
(http://search.cpan.org/src/PYTHIAN/DBD-Oracle-1.19/README.h elp.txt):
"Also: Never copy libclntsh.so to a different machine or Oracle version.
If DBD::Oracle was built on a machine with a different path to
libclntsh.so
then you'll need to set an environment variable, typically
LD_LIBRARY_PATH, to include the directory containing libclntsh.so."
Is this related and if so do you have some advice or guidance I can
share with our computing team that can get this resolved so our
customers don't have to set LD_LIBRARY_PATH to use our tool and we don't
have to develop a wrapper for it?
Thanks so much for any assistance you folks can offer.
Kind regards,
Shannon Kerr
iDEN Networks Infrastructure SCM Team
Motorola, Inc.
------_=_NextPart_001_01C7074A.768AE11E--