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

ROUND AND TRUNCATE FUNCTIONS WITH DB2_COMPATIBILTY_VECTOR=ORA GIVES
EXPONENT RESULT FORM FOR CALCULATION.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When using Oracle application number mode semantics via 
DB2_COMPATIBILTY_VECTOR 
settings of: 
ORA (enable full Oracle compatibility) 
0x10 (enable only Oracle number mode semantics) 
 
The ROUND FUNCTION incorrectly converts the output to normalized 
exponent form: 
 
db2 select round(3344*3/23*3,-1) from sysibm.sysdummy1 
 
1 
------------------------------------------ 
                                   1.31E+3 
 
The correct format in the above example should be: 
1310 
 
The TRUNCATE function also has the same issue.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 7.                      * 
****************************************************************
Local Fix:
Cast calculation with INT : round(INT(3344*3/23*3),-1)
Solution
First fixed in Version 10.5 Fix Pack 7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.12.2014
25.01.2016
28.04.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList