IBM Support

IT04408: SQLSTATISTICS ROUTINE, CLI/ODBC SQLSTATISTICS CALL, JDBC GETINDE XINFO CALL RETURN SQLCODE -413 FOR LARGE VALUES OF CARDINALITY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error 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.
    

Local fix

Problem summary

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

Problem conclusion

  • The problem is fixed in DB2 9.7 FP11
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT04408

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-09-16

  • Closed date

    2015-10-07

  • Last modified date

    2015-10-07

  • APAR is sysrouted FROM one or more of the following:

    IC84214

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSY

       UP

  • RA10 PSY

       UP

  • RA50 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
07 October 2015