The reason I don't think it has anything to do with DBD is that, as I said,
I have been able to use a script which calls DBD::Oracle not running under
mod_perl and everything works great. This is on the same box that dies when
calling DBD through mod_perl. And again, the same script, when run on a
different box with the same verison of DBI and DBD, runs fine. Therefore,
if the problem does lie in the communication with DBD as per your
hypothesis), it must be a mod_perl communication problem, as "regular" Perl
is able to use the same module and talk to Oracle without a hitch...
For reference, my hw/sw is:
Solaris 2.7 (gcc)
Oracle 8.0.6
Perl 5.005_03
mod_perl 1.21
Apache 1.3.9
DBI 1.13
DBD::Oracle 1.03
What I find odd is that all of the sudden people seem to be coming out of
the woodwork about this stuff. Whe I searched through mailing list
archives, some of them going back years, I found something odd... Many
people were talking about this same problem between December of last year
and January of this year. No one found a satisfactory solution (at least, I
didn't see one). Some blamed it on pre-loading CGI.pm in startup.perl,
while others blamed it on having a PerlFreshRestart On in the Apache
confguration scripts. This seems to be a pretty big deal, if so many people
are complaining under so many configurations, and apparently it has gone on
for over a year.
Jason Simms
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
