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 IC88642 Status: Closed

"DB2 -A" RETURNS UNEXPECTED SQLSTATE WHEN AN ADJUSTMENT WAS MADE
TO THE INVALID DATE CALCULATED USING DATE() WITH LITERAL VALUE.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If we force to calculate an impossible date like 02/30/2012, it 
will be adjusted to 02/29/2012 and the warning with SQLSTATE 
01506 should be returned. (Note that 2012 is a leap year.) 
 
SQLSTATE 01506: An adjustment was made to a DATE or TIMESTAMP 
value to correct an invalid date resulting from an arithmetic 
operation. 
 
For example: 
$ db2 conect to sample 
 
$ date 
Fri Aug 17 05:11:20 EDT 2012 
 
$ db2 -a "values date('08/17/2012') + 13 day - 6 month" 
 
1 
---------- 
02/29/2012 
 
  1 record(s) selected. 
 
 
SQLCA Information 
 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: 0   sqlerrml: 0 
 sqlerrmc: 
 sqlerrp : SQLRI01F 
 sqlerrd : (1) -2147221503      (2) 1                (3) 0 
           (4) 0                (5) 0                (6) 0 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)       (11) 
 sqlstate: 00000 --> This should be 01506. 
 
However, if we use "current date", the warning is returned 
properly. 
 
$ db2 -a "values date(current date) + 13 day - 6 month" 
 
1 
---------- 
02/29/2012 
 
  1 record(s) selected. 
 
 
SQLCA Information 
 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: 0   sqlerrml: 0 
 sqlerrmc: 
 sqlerrp : SQL09074 
 sqlerrd : (1) 0                (2) 0                (3) 0 
           (4) 0                (5) 0                (6) 0 
 sqlwarn : (1) W    (2)      (3)      (4)        (5)       (6) 
           (7) W    (8)      (9)      (10)       (11) 
 sqlstate: 01506
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 FixPack 2                            * 
****************************************************************
Local Fix:
Not available
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.1 FixPack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.11.2012
08.01.2013
08.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList