[EMAIL PROTECTED] wrote:
Hello John
I think you shot very well and very fast :-)
I compiled DBD::Oracle with the 32 client of Oracle 9i that is installed in
64bit too.
So because NLS data in Oracle 9i are stored by default in
/app/oracle/product/9.2.0/enterprise64bit/ocommon/nls/admin/data
I set the ORA_NLS33 to this path (I set ORA_NLS33 because I am using within
Perl the Oracle 9i client library).
And then it works !
I am glad It was sort of a wisdom guess on my part. I have never used
32/64 bit boxes but I have seen lots of posts on this vain
So I am happy : it works but I am confused now.
Did I do something wrong ?
No nothing these configuration snafus happen all the time especially
when working on 32/64 bit boxes
My environment is a mix of Oracle 9i and Oracle 10g installed in 64bit on
different Unix
I decided to build DBD::Oracle with Oracle 9i, perhaps would it be better to
compile with Oracle 10g.
And for Perl scripts, perhaps is it better to set variables inside the script
itself instead of using variable of environment ?
I test that too it works.
Do you have recommendations in regards with your experience ?
The instant client might be what you it has a very small footprint.
As for setting the variables in the script I think that will make you
code work for a entire environment and removes possiable users problems
who might have different setting that override or confuse DBD::Oracle or
Oracle. Of course it all depends on what you are going to use the script
for and who is using it. So short answer Yes with a But, Long Answer No
with a Maybe.
Cheers
