Meanwihle I see something clearer.
Seeing that my database related errors based on a misconfigured
application and not on Oracle or DBD problems, I recognized that our error
message doesn't mean what it says. And this could be a good finding relate
to the libclntsh.so.10.1 issue.
The behaviour
On Sep 4, 11:35 am, [EMAIL PROTECTED] (Krivenok Dmitry) wrote:
Hello!
I've developed a perl script that works with Oracle via DBI and
DBD::Oracle.
This perl script illustrates a strange problem while fetching
LONGs and LONG RAWs.
Please look at this code:
Check the Changes file. (Including beyond 1.54 to see any problems in 1.54.)
Tim.
On Tue, Sep 04, 2007 at 02:23:49PM -0700, Ian Burrell wrote:
Is DBI backward compatible with DBD drivers built against older
versions of DBI? We are finally upgrading DBI from 1.38 to 1.54. We
are going to
On 04/09/07 17:44, Bruce Sears wrote:
the solution i found is this: i moved the directory containing
libclntsh.so (and associated others) under /usr/lib, which is a location
that apache seems to trust, as opposed to where i had originally placed
this directory. to be precise, when i
As stated in the README file i'm reporting issues compiling DBD::Oracle
on Solaris 10
i apologize if this is not the correct place to do it :)
REPORT
Platform is Solaris 10 on Sun Fire T2000
Compiling DBD::Oracle, 'make' stage fails with output:
Looks like you are trying to compile the 32 bit oracle client with 64 bit
system. I think you have to use the 64 bit oracle client.
- Original Message -
From: toni garcia [EMAIL PROTECTED]
To: dbi-users@perl.org
Sent: Wednesday, September 05, 2007 10:56 AM
Subject: report (problems
On 9/5/07, John Scoles [EMAIL PROTECTED] wrote:
Looks like you are trying to compile the 32 bit oracle client with 64 bit
system. I think you have to use the 64 bit oracle client.
My interpretation is that it is a 32-bit Perl (see longsize=4 and
-xarch=v8 in the compiler options). The link
