Hi,
I am getting a very strange behaviour in trying to use DBD::Oracle to connect to a database. From the command line I can connect to a local database using TWO_TASK or ORACLE_SID so the link to the database is fine. However if I have a script of the following form:
$ENV{ORACLE_SID}="grumpy"; my $dbh = DBI->connect( "dbi:Oracle:","sneezy","sneezy" ); my @output = `echo hi`; printf "Job status: %d\n", $?; exit;
I get a job status of -1 although the command has run successfully. It doesn't matter what command I give it is always -1. If I replace $ENV{ORACLE_SID} with $ENV{TWO_TASK} = "grumpy" then the job status comes out with 0. So I am presuming that DBD::Oracle is polluting perl in some manner if the ORACLE_SID is set? Why though and is there a way to get the system to perform in a "normal" way.
The problem occurs on Red Hat Linux 5.6 (and on Solaris 10) in a 64-bit environment with Oracle 11g. I've tried both DBD::Oracle 1.20 and 1.27. Has anyone else had this problem? Thanks.
Fairchild.
In reply to Strange behaviour with DBD::Oracle by Fairchild
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |