DB2 FOR LUW / DB2FORLUW / 970 - DB2

When using the IW option of the format string syntax of 
converting a timestamp to an iso week, a query may incorrectly 
return the iso 
week of 53, when the correct answer should have been 52. 
 
For example: 
db2 values to_char(TIMESTAMP('2011-01-01'),'IW'); 
 
1 
 
----------------------- 
53 
 
 
  1 record(s) selected. 
 
The correct answer here should have been 52. 
 
This incorrect result will only occur if ALL of the following 
conditions are true: 
1. The date being converted is one of the first few days of the 
year such  that these days actually belong to the last ISO week 
of the previous   year. 
 
2. Jan 1st of this year falls on a Saturday. 
 
3. Jan 1st of the previous year is not a Thursday.

Instead of using the IW format string directly, the function 
week_iso() can be used instead, and then convert that answer to 
a char. 
for example: 
db2 values to_char(week_iso(TIMESTAMP('2011-01-01')))

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
 

not known / see Local fix

Fixed the problem

forerunner  : APAR is sysrouted TO one or more of the following: IC81980 IC83680 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

12.03.2012
29.03.2013
29.03.2013