home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC67359 Status: Geschlossen

SELECT QUERY ON DATATYPE DATE AND REGISTER CURRENT DATE WITHIN STORED
PROCEDURE MAY RETURN UNEXPECTED RESULT ON SOME LOCALES

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL who are using locale with 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.7 FixPack 3.                            * 
****************************************************************
Local-Fix:
Not available.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 9.7 FixPack 3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.03.2010
27.09.2010
27.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList