DB2 FOR LUW / DB2FORLUW / 980 - DB2

The problem may occur under the following scenarios. 
 
1. Using a locale with the date format other than following, for 
example, Australian English. 
     ISO yyyy-mm-dd 
     USA mm/dd/yyyy 
     EUR dd.mm.yyyy 
 
2. Running a select query on datatype DATE and register CURRENT 
DATE within stored procedure. 
   CHAR(CURRENT DATE) will not cause the problem. 
 
Here is an example on Australian English locale. 
 
CREATE PROCEDURE S1.TEST1() 
    SPECIFIC S1.TEST1 
    DYNAMIC RESULT SETS 1 LANGUAGE SQL P1: 
BEGIN 
        Declare c_Hits Cursor with return for 
        SELECT CURRENT DATE AS DATE1 
        from sysibm.SYSDUMMY1; 
        Open c_Hits; 
END P1 
 
 
$ db2 call TEST1 
 
  Result set 1 
  -------------- 
 
  DATE1 
  ---------- 
  0022-65534 
 
  1 record(s) selected. 
 
  Return Status = 0

**************************************************************** 
* USERS AFFECTED:                                              * 
* All who use a locale with the date format other than         * 
* ISO(yyyy-mm-dd)/USA(mm/dd/yyyy)/(EUR dd.mm.yyyy).            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* As same as Error description.                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.8 FixPack 4.                            * 
****************************************************************

Not available.

DB2 Version 9.8 Fix Pack 4 for AIX and Linux
 DB2 Version 9.8 Fix Pack 5 for AIX and Linux
 

Problem was first fixed in DB2 UDB Version 9.8 FixPack 4.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

01.04.2010
04.08.2011
04.08.2011

9.8.FP4