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

INCORRECT OUTPUT OF DATETIME AND DATETIME2 IN SQL SERVER

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
There are 2 issues failed for round-up issue when fetch data 
from SQL SERVER datetime/datetime2 column in v97fp7. 
 
Issue 1: Select from nickname where the query condition is a 
timestamp column from local table, the output is incorrect. 
SELECT * FROM t83131 
C1 
-------------------------- 
2010-05-06-00.00.00.000000 
 
  1 record(s) selected. 
 
SELECT max(c1) FROm t83131_db2 
C1 
-------------------------- 
2010-05-05 23:59:59.999000 
 
-- With DB2 9.7 FP5 
SELECT * FROM t83131 where c1=(SELECT max(c1) FROm t83131_db2) 
 
C1 
-------------------------- 
2010-05-06-00.00.00.000000 
 
  1 record(s) selected. 
 
-- With DB2 9.7 FP7 
SELECT * FROM t83131 where c1=(SELECT max(c1) FROm t83131_db2) 
 
C1 
-------------------------- 
- 
 
  0 record(s) selected. 
 
 
Issue 2: Select from nickname where the query condition is a 
timestamp constant string, the output is incorrect. 
SELECT * FROM t83131 
C1 
-------------------------- 
2010-05-06-00.00.00.000000 
 
  1 record(s) selected. 
 
SELECT max(c1) FROm t83131_db2 
C1 
-------------------------- 
2010-05-05 23:59:59.999000 
 
-- With DB2 9.7 FP5 
SELECT * FROM t83131 where c1= '2010-05-05 23:59:59.999' 
 
C1 
-------------------------- 
2010-05-06-00.00.00.000000 
 
  1 record(s) selected. 
 
-- With DB2 9.7 FP7 
SELECT * FROM t83131 where c1= '2010-05-05 23:59:59.999' 
 
C1 
-------------------------- 
- 
 
  0 record(s) selected.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* INCORRECT OUTPUT OF DATETIME AND DATETIME2 IN SQL SERVER     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to versiom 10.1 fixpack 3.                           * 
****************************************************************
Local Fix:
available fix packs:
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
This is fixed in version 10.1 fixpack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.04.2013
30.10.2013
30.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList