|
Problem IT04412
|
Status: Closed |
SQLSTATISTICS ROUTINE, CLI/ODBC SQLSTATISTICS CALL, JDBC GETINDE XINFO CALL RETURN SQLCODE -413 FOR LARGE VALUES OF CARDINALITY |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 V10.1 Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.1 Fix Pack 5 or higher. *
**************************************************************** |
| Local Fix: |
|
| Solution |
Fixed in DB2 V10.1 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.09.2014
13.07.2015
13.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
