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

DB2 CAN RETURN WRONG RESULTS WHEN USING THE SPECIAL REGISTER 'CURRENT
DECFLOAT ROUNDING MODE' IN A QUERY IN AN MPP ENVIRONMENT

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Wrong results can be returned as shown:

create table t1 (c1 int, c2 varchar(128)) organize by row
distribute by (c1);
insert into t1 values
(1,'ROUND_HALF_EVEN'),(2,'ROUN'),(3,'ROUN'),(4,'ROUN'),(5,'ROUN'
),(6,'ROUND_HALF_EVEN'),(7,'ROUND_HALF_EVEN'),(8,'ROUN'),(9,'ROU
N');


In MPP(4 nodes) :
 select * from t1 where CURRENT DECFLOAT ROUNDING MODE = t1.c2

C1          C2

-----------
----------------------------------------------------------------
----------------------------------------------------------------

  0 record(s) selected.

We expect this query to return 3 records.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description. Install release and fixpak that has   *
* this fix.                                                    *
****************************************************************
* RECOMMENDATION:                                              *
* Install release and fixpak that has this fix.                *
****************************************************************
Local Fix:
n/a
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT18500 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.12.2016
30.05.2017
30.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)