Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the DBD-Oracle CPAN distribution.

Report information
The Basics
Id: 22623
Status: resolved
Priority: 0/
Queue: DBD-Oracle

People
Owner: Nobody in particular
Requestors: msoffen [...] iso-ne.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 1.18a
Fixed in: (no value)



Subject: Trailing slash with ORACLE_HOME causes OCIEnvNlsCreate error
If your ORACLE_HOME environment is has a trailing slash, in DBD-Oracle-0.18a, the ->Connect will fail. For Example. If you have ORACLE_HOME set to /oracle/product/10.2/ you get the following error: DBI connect('pubdbd','www_xfer',...) failed: ERROR OCIEnvNlsCreate. Check ORACLE_HOME env var, NLS settings, permissions, etc. at blah.blah.blah line xxx If you remove the trailing slash, the script works fine. This is under perl 5.8.5 on a Centos 4.4 (Final) machine.
I think this is a simple misconfiguation of the ORACLE_HOME on you box. I checked a number of DBAs here and it is not normal DBA pratice to use a trailing slash on ORACLE_HOME. Oracle (in Lunix anyway) will just ignore // when the system tries to find subdirs and libs however DBD::Oralce is compiled so it might have problems doing this. Best advice here is to remove the trailing slash from you ORACLE_HOME unless you need it for your OS is it really required in your OS. If that is the case I will have to write get a patch to get around this.