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

COLUMNAR ONLY: POSSIBLE WRONG RESULT IN EQUALITY JOIN WHEN COMPARING ZERO
BINARY FLOATING POINT VALUE

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Prerequisites:
- PowerPC platform
- Equality join executed in Columnar Logic (under CTQ in the
plan, for example)
- Unary minus used on join predicate on a REAL or DOUBLE value
and value is 0.0

Sample:
create table state(floatnr double, state varchar(20)) organize
by column;
insert into  state values(+0.0, 'CALIFORNIA');
insert into  state values(+1.0, 'TEXAS');
insert into  state values(+2.0, 'OREGON');
insert into  state values(+3.0, 'FLORIDA');

SELECT Y.FLOATNR, Y.STATE FROM STATE Y, STATE X WHERE X.FLOATNR
= -Y.FLOATNR;

FLOATNR                  STATE
------------------------ --------------------

  0 record(s) selected.

Expected result:
FLOATNR                  STATE
------------------------ --------------------
  +0.00000000000000E+000 CALIFORNIA

  1 record(s) selected.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
****************************************************************
Local Fix:
db2set DB2_CDE_HW_SIMD=13
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.08.2018
27.11.2018
27.11.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)