RE: DBD Oracle module
- From: shannon.kerr@xxxxxxxxxxxx (Kerr Shannon-SKERR1)
- Date: Thu, 16 Nov 2006 12:51:41 -0500
Thanks for the reply. The Oracle client libraries are installed at the
same location on all of our servers (Solaris 2.6 and 2.8). I believe
the problem is with the configuration and/or installation procedure and
that's why the libraries are not found on Solaris 2.6 (and so we set
LD_LIBRARY_PATH) but are found on Solaris 2.8 as they should be (without
setting LD_LIBRARY_PATH). The computing team believes they have the
proper installation, but I don't understand why we have this issue only
on Solaris 2.6 if the installation is correct.
---------------------------
don'tIs 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
have to develop a wrapper for it?
If you don't control where the customer is going to install
Oracle's client libraries, then its impossible to a priori set the
runtime link path for DBD::Oracle's Oracle.so.
With Oracle Instant Client and Solaris 7 and newer, you might be
able to use $ORIGIN.
See Dave Barr's "Why LD_LIBRARY_PATH is bad"
<URL:http://xahlee.org/UnixResource_dir/_/ldpath.html>
John
groenveld@xxxxxxx
.
- Follow-Ups:
- Re: DBD Oracle module
- From: John D Groenveld
- Re: DBD Oracle module
- References:
- Re: DBD Oracle module
- From: John D Groenveld
- Re: DBD Oracle module
- Prev by Date: Re: Creating XML from an Oracle DB
- Next by Date: Re[2]: How should I connect via DBD::Oracle to efficiently obtain 2000+ simultaneous connections?
- Previous by thread: Re: DBD Oracle module
- Next by thread: Re: DBD Oracle module
- Index(es):
Relevant Pages
|
|
