IBM Support

IT09595: SYSIBM.POWER ( EXPRESSION1, EXPRESSION2 ) WILL RETURN INCORRECT RESULTS FOR SOME VALUES WHEN THE BIGINT DATA TYPE IS USED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The POWER scalar function will return incorrect results for
    certain values if at least one BIGINT argument is used.
    
    The following is a list of values that will produce incorrect
    results:
    
    Case (1) Argument 1 is 2 or -2 and argument 2 is -1.  The
    correct result is to be 1 if argument 1 is 2 and -1 if argument
    1 is -2, but 0 is returned instead.
    
    Case (2) Argument 1 is -1 and argument 2 is less than 0.  The
    correct result is to be -1 if argument 2 is odd and 1 if
    argument 2 is even, but 0 is returned instead.
    
    Case (3) Arguments 1 and 2 are both 0.  The correct result is 1,
    but an overflow error (SQL0802N; SQLSTATE=22003) is returned
    instead.
    
    For example, the value in each column should be -1, but instead
    the value in columns 2, 3, and 4 is 0.
    
    values(power(-1,-1), power(bigint(-1),-1), power(-1,bigint(-1)),
    power(bigint(-1),bigint(-1)))
    
    1           2                    3                    4
    ----------- -------------------- --------------------
    --------------------
             -1                    0                    0
    0
    
      1 record(s) selected.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 version 10.1.0.5.                             *
    ****************************************************************
    

Problem conclusion

  • The problem is first fixed in DB2 version 10.1.0.5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT09595

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-06-22

  • Closed date

    2015-07-10

  • Last modified date

    2015-07-10

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

    IT06646

  • 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

  • RA10 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
10 July 2015