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

DB2BATCH RESULTSET OUTPUT RETURNS WRONG FRACTION PART FOR TIMESTAMP VALUES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2BATCH returns wrong fraction part for TIMESTAMP values. 
 
Following steps will reproduce the issue: 
 
create table t (testno INTEGER , testtime TIMESTAMP ); 
insert into t values ( 1 , '2011-04-01 00:00:01.000001' ); 
insert into t values ( 2 , '2011-04-01 00:00:01.000010' ); 
insert into t values ( 3 , '2011-04-01 00:00:01.000123' ); 
insert into t values ( 4 , '2011-04-01 00:00:01.001234' ); 
select * from t order by testtime asc ; 
 
 
Output when running SELECT with db2 clp is correct: 
 
TESTNO      TESTTIME 
----------- -------------------------- 
          1 2011-04-01-00.00.01.000001 
          2 2011-04-01-00.00.01.000010 
          3 2011-04-01-00.00.01.000123 
          4 2011-04-01-00.00.01.001234 
 
 
But running db2batch -d sample -f b.sql (contains "select * from 
t order by testtime asc ;"): 
 
* SQL Statement Number 1: 
select * from t order by testtime asc ; 
 
TESTNO      TESTTIME 
----------- -------------------------- 
          1 2011-04-01 00:00:01.001000 
          2 2011-04-01 00:00:01.010000 
          3 2011-04-01 00:00:01.123000 
          4 2011-04-01 00:00:01.1234000
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5.                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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

Solution
First fixed in Version 9.7 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.05.2011
12.12.2011
12.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList