vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello people! I have a strange problem with some stored procedures here is a sample of a stored procedure that has a problm with the dates. CREATE PROCEDURE TEST_DATE (OUT G_LAST_DATE DATE) LANGUAGE SQL ------------------------------------------------------------------------ --================================================== ==================== P1: BEGIN select start_date into G_LAST_DATE from date_info; END P1 The developers say to me that for example when they did an output of the G_LAST_DATE parameter it showed 2004-11-03 Now it shows 2004-03-11. They say that they need the previous. Their stored procedures cancel now. From the above select statement there is a date_info table. Here are the results from it when you select from that table. The above statement used to work, now it give the following error: CLI0113E An invalid datetime format was detected; that is, an invalid string representation or value was specified. db2 "select * from date_info" START_DATE ---------- 29/10/2004 1 record(s) selected. All this happen they say after the reinstallation of DB2 and after I applied FixPak11. Previously the AIX was 4.3.3 with DB2 V7.2 and Fixpak 6 and now its AIX 5.2 with DB2 V7.2 and Fixpak 11. Any ideas how to tackle this problem? Thanks |
| |||
| This smells like the region/client code page information was messed up. Presuming you gave us a simplified example you must have a CHAR(<date>) fucntion soemwhere (expicitly, or implicitly at bind-out?): >>-CHAR--(--datetime-expression--+--------------+--)----------->< '-,--+-ISO---+-' +-USA---+ +-EUR---+ +-JIS---+ '-LOCAL-' You hicup is likely in tha 'LOCAL' which is, I believe the default. Cheers Serge |
| ||||
| Serge Rielau wrote: > This smells like the region/client code page information was messed up. > Presuming you gave us a simplified example you must have a CHAR(<date>) > fucntion soemwhere (expicitly, or implicitly at bind-out?): > > >>-CHAR--(--datetime-expression--+--------------+--)----------->< > '-,--+-ISO---+-' > +-USA---+ > +-EUR---+ > +-JIS---+ > '-LOCAL-' > > You hicup is likely in tha 'LOCAL' which is, I believe the default. > > Cheers > Serge On second thought... It looks more like the DATE function or bind-in... |
| Thread Tools | |
| Display Modes | |
|
|