DB2 - Problem description
| Problem IT09596 | Status: Closed | 
| SYSIBM.POWER ( EXPRESSION1, EXPRESSION2 ) WILL RETURN INCORRECT RESULTS FOR SOME VALUES WHEN THE BIGINT DATA TYPE IS USED | |
| product: | |
| DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem 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. | |
| Problem Summary: | |
| **************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.5.0.7. * **************************************************************** | |
| Local Fix: | |
| Solution | |
| The problem is first fixed in DB2 version 10.5.0.7. | |
| Workaround | |
| not known / see Local fix | |
| Timestamps | |
| Date - problem reported : Date - problem closed : Date - last modified : | 22.06.2015 19.01.2016 11.07.2016 | 
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.7 |  | 







 
