DB2 - Problem description
Problem IC76491 | Status: Closed |
DB2BATCH RESULTSET OUTPUT RETURNS WRONG FRACTION PART FOR TIMESTAMP VALUES | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - 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.5 FixPack 9. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
First fixed in Version 9.5 FixPack 9. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 19.05.2011 14.03.2012 14.03.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.9 |