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

DECIMAL PRECISION DIFFERENCE IN JDBC WITH ORA & NON-ORA SETTING

product:
DB2 CONNECT / DB2CONNCT / A50 - DB2
Problem description:
Both DB2 & JCC rounds down double(decimal) values by default.
But when server is set with ORA compatibility, Db2 changes the
behavior, and it rounds up the value. JCC has no way of knowing
if ORA compatibility is set or not. To solve this problem, JCC
will send all decimal values as it is without any truncation to
server, and server will do the truncation according to its
settings.

This change in behavior is applicable only to Db2 on LUW server
and jcc default behavior holds good for all other database
servers.

problem is fixed via a SB 4.19.81 in Db2 V10.5.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Db2 JCC users                                                *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 V11.1.4.7                                     *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Db2 JCC users                                                *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 V11.1.4.7                                     *
****************************************************************
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.03.2022
28.03.2022
24.10.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)