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

"CLI0111E NUMERIC VALUE OUT OF RANGE" IF THE LENGTH OF THE
DECFLOAT DATA IS LONGER THAN 31 DIGITS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When fetching DB DECFLOAT data into DECIMAL output columns CLI 
returns a ?CLI0111E  Numeric value out of range.? , if  the 
length of the DECFLOAT data is longer than 31 digits. 
 
For example: 
 
VALUES ( CAST ( '1.000000000000000000000000000000' AS DECFLOAT ) 
) 
      can be fetched without problems via CLI into a DECIMAL( 
N,3 ) resulting in value 1.000. 
 
VALUES ( CAST ( '1.0000000000000000000000000000000' AS DECFLOAT 
) ) 
      returns a ?CLI0111E  Numeric value out of range.? If you 
try to fetch this via CLI into a DECIMAL( N,3 )
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 4.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.5 Fix Pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.03.2014
20.10.2014
20.10.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList
10.5.0.5 FixList