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

FLOATING POINT TO DECIMAL CONVERSION IN ORA MODE CAN RESULT IN LESS
ACCURATE RESULTS FOR NUMBERS WITH LARGE SCALE

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
This APAR is done as a temporary internal workaround 
for a specific customer. This APAR is not a problem and can be 
ignored by any users. 
 
As per IEEE 754 standard for floating point datatypes, floating 
point numbers are a binary approximation of an actual number. 
As such, when these datatypes are stored, there is potential for 
a loss of accuracy. For some numbers, in particular 
(but not limited to) those numbers that have a large amount of 
scale digits, this gives a number that may lose the 
precision and accuracy that is needed in some applications. 
 
In DB2, the floating point datatypes are DOUBLE, FLOAT, and REAL 
(see documentation about DB2 datatypes). If having precision and 
accuracy is required for the application, then it is not 
recommended to use floating point types, and the DECIMAL or 
DECFLOAT datatype should be used instead. 
 
This APAR provides an alternate approach from float to decimal 
for some numbers that are suffering from the 
binary approximation accuracy concerns. 
 
Since this is a behaviour change in how floating point numbers 
are treated by DB2, this change is not provided for general use. 
 If this APAR is required, then please contact DB2 support team, 
who can provide guidance on how to enable this alternate mode 
for converting floating point types to DECIMAL.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher               * 
****************************************************************
Local Fix:
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in Db2 11.1 Mod 3 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.07.2017
19.03.2018
19.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)