home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT01118 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.5.4.                                          * 
****************************************************************
Local Fix:
available fix packs:
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

Solution
Day/Month name function return values as per Gregorian calendar
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.04.2014
08.09.2014
08.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList