Try to write a CGI that generates the whole error message as valid output,
something like this:
#!/usr/bin/perl
eval "use DBI;";
print "Content-Type: text/plain\n\n";
if ($@) {
print "The error was $@";
} else {
print "There was no error, weird";
}
Then you can see the whole message. Maybe that will give you a hint.
On Fri, 16 Aug 2002, darrefo wrote:
> I have encountered a peculiar problem involving the DBI, although I
> have no evidence to suggest the DBI is the cause of the problem.
>
> I am running Solaris 8 and using the iPlanet 6.0 (I guess now called Sun
> One)
> web server. I have a load of perl CGI scripts talking to an Oracle 9i
> database
> on another Solaris box.
>
> I configured the system with:
>
> Perl 5.8.0
> DBI 1.30
> DBD-Oracle 1.12
>
> and compiled the DBD with the 9i client software in 32 bit mode.
> Everything
> was compiled on the machine using gcc.
>
> When I try to execute a script that calls the database, I get an error:
>
> "the CGI program did not produce a valid header (name without value:
> got line "begin failed -- compilation aborted at /my_path/dbi.pm line
> 189")"
>
> The script will work without error from the command line.
>
> The problem seems to lie in some weird iPlanet/Perl 5.8.0/DBI
> interaction that I dont understand, because:
>
> 1) I dont need to make any calls in the script to get the error -
> simply having the line "require DBI" (or "use DBI") in the
> script causes the error
>
> 2) If I switch to Perl 5.6.1, everything works fine.
>
> Any ideas out there?
>
> Darrell Oresky
>
>
- D
<[EMAIL PROTECTED]>
