DB2 FOR LUW / DB2FORLUW / 970 - DB2

Currently, the SYSIBM.SQLSTATISTICS routine and the 
corresponding CLI/ODBC SQLStatistics () andd JDBC getIndexInfo 
calls, return SQLCODE -413 (Overflow occurred during numeric 
data type conversion) if the CARDINALITY returned exceeds 
2147483647. 
 
Per the ODBC specification,  we return CARDINALITY as INTEGER. 
However it is defined as BIGINT in the referenced table 
SYSIBM.SQLSTATISTICS. So, the SQLSTATISTICS routine CASTSs 
CARDINALITY to INTEGER before returning this value. 
 
If the CARDINALITY value returned is greater than the maximum 
allowable INTEGER value (2147483647), then a numeric overflow 
error will occur on the data type conversion (SQLCODE -413). 
 
The design will be changed to return 2147483647 (largest INTEGER 
value) when CARDINALITY cannot fit into INTEGER. 
 
This design is consistent with other IBM-defined views and 
routines which reference CARDINALITY. 
 
This is the same issue as DB2 9.7 APAR IC70444.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP11 or later                             * 
****************************************************************

The problem is fixed in DB2 9.7 FP11

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

16.09.2014
07.10.2015
07.10.2015

9.7.FP11