Informix\\\\Perl error.
Group, I have two issues: We're trying to move our server currently on Windows Server 2000 to a new Windows Server 2003 box. Since the new box does not have informix installed on it, we are using informix ODBC drivers. 1. One of the problems was a date formatting error when retrieving from the database. The default dates are being pulled out as YYYY-MM-DD instead of the MDY4 format of MM/DD/YYYY. How do we set the formatting of the date being pulled? 2. When we instead reformat some of the dates being retrieved from the database, and remediating our perl code to make it work, all but 1 lone perl script works, and I fear this is a show stopper. We get an access violation on an informix dll, and the executable perl code is forced to terminate. Does anyone have any exposure to the following error? Correction suggested? Faulting application perl.exe, version 5.10.0.1002, faulting module iclit09bW.dll, version 3.80.0.10841, fault address 0x0001f711. Thanks, ************************************** Ernie Knox Sears Holding Co. IT Database Administrator Specialist IT Service Management, Strategy & Architecture 3333 Beverly Rd., B4-266A Hoffman Estates, IL. 60179 Office: (847) 286-5735 Fax: (847) 645-3874 Pager: (800) 759-8352 Pin#: 7271042 Email: eknox@sears.com " It's always a great day to watch Football ! " **************************************
On Jan 30, 2008 2:17 PM, Knox, Ernest <eknox@searshc.com> wrote: > Group, I have two issues: > > We're trying to move our server currently on Windows Server 2000 to a > new Windows Server 2003 box. Since the new box does not have informix > installed on it, we are using informix ODBC drivers. So you are using DBD::ODBC? Which version of that? Which version of DBI? Which version of CSDK is providing the ODBC drivers? > 1. One of the problems was a date formatting error when retrieving > from the database. The default dates are being pulled out as YYYY-MM-DD > instead of the MDY4 format of MM/DD/YYYY. How do we set the formatting > of the date being pulled? This could depend on a lot of things - what have you tried? Specifically, does setting DBDATE help? It could well be that the code in DBD::ODBC expects the DATE type to be formatted as an SQL DATE should be formatted - which is in the ISO 8601 notation such as 2008-01-31. And it might then provide no way to deal with it. You can easily enough transform date strings to your desired format: $datevar =~ s%^(\\\\d{4})-(\\\\d\\\\d)-(\\\\d\\\\d)$%$2/$3/$1%; However, having to remember to do that is error-prone. I don't have a good solution for you if DBDATE won't serve the turn. > 2. When we instead reformat some of the dates being retrieved from > the database, and remediating our perl code to make it work, all but 1 > lone perl script works, and I fear this is a show stopper. We get an > access violation on an informix dll, and the executable perl code is > forced to terminate. > > Does anyone have any exposure to the following error? Correction > suggested? > > Faulting application perl.exe, version 5.10.0.1002, faulting module > iclit09bW.dll, version 3.80.0.10841, fault address 0x0001f711. Which version of Perl (5.10.0, and probably an ActiveState build, but ...) I assume you are using 32-bit Windows since you're on Win2K3. I don't have much help to offer. If you aren't on the most recent DBI and DBD::ODBC, then an upgrade is worth trying. Ditto with the ODBC driver itself, of course. -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2007.0914 -- http://dbi.perl.org/ NB: Please do not use this email for correspondence. I don't necessarily read it every week, even.