|
Problem IC67358
|
Status: Closed |
SELECT QUERY ON DATATYPE DATE AND REGISTER CURRENT DATE WITHIN STORED PROCEDURE MAY RETURN UNEXPECTED RESULT ON SOME LOCALES |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
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 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error description field for more information. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.5 FixPack 6. *
**************************************************************** |
| Local Fix: |
Not available. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 UDB Version 9.5 FixPack 6. |
| Workaround |
see LOCAL FIX. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67359 IC67579
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.03.2010
22.06.2010
22.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
