Hello,
Last month I reported a problem I was having with testing the DBD Oracle
module on Oracle 9.2.0.2. The tests were failing on the CLOB section.
It turns out that my problem was due to my database character set having
been UTF8 based. Resetting the NLS_LANG env to a non UTF8 character set
re
Hello again,
Has anyone managed to build DBD-Oracle on the latest version of Oracle (9i
Release 2 i.e. 9.2.0 - not 9.0.1) on Solaris or indeed any platform. I
posted a problem with CLOB tests previously - but have to yet to find a
solution.
Thanks,
Ben.
Okay,
> It would be good if you could hack the Makefile.PL to get the build
> rule discovery to work.
I have hacked the Makefile.PL so that it can work out the build rule:
New output from perl Makefile.PL -v:
...
Attempting to discover Oracle OCI build rules...
gcc -B/usr/ccs/bin/ -c DBD_O
Hello again,
I am still not having any luck in getting the tests to pass. It appears to
be the CLOB re-reading that is failing.
I have checked all the usual places for help. I have also tried creating a
test stub that does a similar thing to the failed tests.
Below is the full set of informatio
Hello.
I am having some problems testing DBD-Oracle-1.12 in the following
environment:
Solaris 9
Perl 5.8.0
Oracle 9.2.0.2.0
DBI 1.32
Compilation is fine.
Output from test stage is:
PERL_DL_NONLAZY=1 /usr/local/bin/perl "-MExtUtils::Command::MM" "-e"
"test_harness(0, 'blib/lib', 'blib/arch')" t
Hello,
Can anyone explain why the long tests fail if the Oracle character set is
set as UTF8?
i.e.
NLS_LANG="ENGLISH_UNITED KINGDOM.UTF8"; export NLS_LANG
make
make test
t/long..ok 97/143Use of uninitialized value in numeric eq (==)
at t/long.t line 230.
# failed test 98 at