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 IT01118 Status: Geschlossen

NOVEMBER AND DECEMBER 1ST-14TH 1582 INCORRECTLY RETURNS JULIAN CALENDAR
DAYS INSTEAD OF USING GREGORIAN CALENDAR

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
As per Western calendar, Gregorian Calendar is used on and after 
15 October 1582.  DB2 incorrectly uses Julian Calendar for 
November 1582 and December 1st-14th 1582. 
 
The APAR may cause incorrect value returned by DAYNAME scalar 
function. 
 
For example the following SQL statements incorrectly returns 
'Thursday' instead of 'Monday'. 
 
VALUES DAYNAME ('1582-11-01');
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.5.4.                                          * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Day/Month name function return values as per Gregorian calendar
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.04.2014
08.09.2014
08.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList