On Tue, 14 Aug 2001, Curt Russell Crandall wrote:
>We've been noticing that often times DBD::Informix is not returning the
>whole error message generated by the database. For example, I received
>the following string in response to a char to numeric conversion error:
>
>SQL:-1213: <
Hmmm; -1213 should say "-1213: A character to numeric conversion process failed."...
>However in the Apache error_log, I get:
>
>FastCGI: server
>"/apache/test/vip2/cgi/user/a03.fcgi" stderr: DBD::Informix::st execute
>failed: SQL: -1213: <<Failed to locate SQL error message> at
>../ip01_ipid_cache.pm line 52.
But that indicates that the error message files were not available so
DBD::Informix could not obtain the text of the error message. That
opens the question - what do you have $INFORMIXDIR set to inside your
FastCGI server, and so on.
>or
>
>FastCGI: server
>"/apache/test/vip2/cgi/user/a03.fcgi" stderr: DBD::Informix::st execute
>failed: SQL: -1213: Character to numeric conversion error at
>../ip01_ipid_cache.pm line 52.
And there's the correct message...
>The behavior of what is included in $DBI::errstr does not seem to
>follow any pattern. Sometimes when I print $DBI::errstr I'll get the
>error message other times I just get the SQL and/or ISAM error.
Do you know the process ID of the FastCGI server(s)? Is there any
chance that the environment is not being set correctly.
>Is anyone aware of a bug in DBD::Informix that is causing this?
I'm not aware of any bug. When a problem like this occurs in a web
environment, there are a few possibilities:
* Environment
* Environment
* Environment
* Possibly the number of file descriptors in use (no available
file descriptors to open the message file?)
>It is rather irritating since I often go to the Informix web site to
>look up the error code, and the web developers decided to dump almost
>2MB of text on that page, thus causing my browser to puke often.
What's up with 'finderr'? Also check out the IIUG (Informix
International User Group) web site (http://www.iiug.org/) and the
software archive - look for chkmsg in the ESQL/C section so you can do
"chkmsg -1213" or "chkmsg -201:-299". And there's also 'listiem' so you
can do "listiem -lh $IXD/msg/en_us/0333/*.iem", etc.
>I'm using Perl 5.6.0, DBI 1.14 and DBD::Informx 1.00.PC1 on AIX 4.3.3.
No major environmental problems visible there...Thanks for including the
info -- which version of CSDK are you using, not that I think it makes
any odds in this problem.
--
Yours,
Jonathan Leffler ([EMAIL PROTECTED]) #include <disclaimer.h>
Guardian of DBD::Informix v1.00.PC1 -- http://www.perl.com/CPAN
"I don't suffer from insanity; I enjoy every minute of it!"
