Make sure the environment variables set in the webserver process are the same as those you have set when you run from the command line. Likely suspects are ORACLE_HOME, TNS_ADMIN, LD_LIBRARY_PATH, PERL5LIB, and SHLIB_PATH, but compare them all. Also make sure the account the webserver process runs in has permission to read all the Perl files and read/execute any binaries used including Oracle's libraries.
There is no need to address messages like this to Tim. He is very busy and most problems can be addressed by someone on the mail list. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. ----- Original Message ----- From: "Shawn Swain" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, October 18, 2001 16:50 Subject: Problem with Oraperl and DBD::ORACLE within CGI scripts > My team upgraded Oracle from 8.0.6 to 8.1.7. It was discovered that the > CGI scripts that use Oraperl to interact with our database would cause a > core dump. At the time we had perl version 5.005_03 installed, Oraperl > v 1.39, DBD::ORACLE v 1.03, and DBI 1.13. I attempted to link to the > new 8.1.7 libraries without success. I decided to install perl v5.6.1 > and the latest versions of DBI, DBD::ORACLE, and CGI. Currently it > appears that the installation was successful because all scripts can be > executed from the command line without errors (as long as SHLIB_PATH is > set). However when I attempt to execute our cgi scripts I run into > problems.
