Hello,
Well I have had to wait for the sysadmins to do this, but we have done
as you recommended and removed all the dbd and then tried doing a make
on the system of the dbd to build a new one.
It has errors relating to the same problem, but we pressed on and
installed anyway
Here is a trace,
Looks like the 64 bit perl vs 32 bit .pms issuesthat is croping up more and
more.
So I would go back one more step at remove all the DBI and get the source
and recompile and insall. the DBD::Oracle again.
What you might want to try is
Not sure what the cure for this is??
Peter McLarty [EMAIL
Hi. Sorry if this turns out to be a newbie mistake, but I've run into an odd
problem while using DBD::Oracle.
For some reason, my sql statement results in empty strings.
Instead of getting the value i want to see there is a '', (please see
below).
The amount of columns (6 in this case) are
On 10/10/07, John Scoles [EMAIL PROTECTED] wrote:
Hi. Sorry if this turns out to be a newbie mistake, but I've run into an
odd
problem while using DBD::Oracle.
For some reason, my sql statement results in empty strings.
[...snip...]
This is the result with the empty strings when using
On Wed, Oct 10, 2007 at 05:22:08PM +1000, Peter McLarty wrote:
Hello,
Well I have had to wait for the sysadmins to do this, but we have done
as you recommended and removed all the dbd and then tried doing a make
on the system of the dbd to build a new one.
It has errors relating to the
Just a wrap up for those that are going to fall prey to this gremlin.
I took over the issue from the SA and removed DBI and DBD from the @inc
paths and then reinstalled them initially it didn't work
As it turned out these DBD files had been installed on a dual core
server and there was some files
