| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IT07562 | Status: Closed |
IN RARE SCENARIOS COMPLEX QUERY WITH AN OLAP SPECIFICATION AND A SUBQUERY MIGHT RETURN EXTRA ROWS | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
A complex query with an OLAP specification and a sub-query might return extra rows. Example of an OLAP query: select c18,c1a,c1f,c15,c16 from mytbrow1 where (c15, c16) in (select min(c25) over (partition by c27, c2b order by c2c, c2h, c20 rows between unbounded preceding and current row) as min, c36 from mytbrow2, mytbrow3 where mytbrow1.c14 = mytbrow2.c24 and mytbrow2.c21 = mytbrow3.c31) order by c18, c1a, c1f; Internal information about the query needs to be reviewed by DB2 support to confirm that the query is not affected. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.1.0.5. * **************************************************************** | |
| Local Fix: | |
| Solution | |
The problem is first fixed in DB2 version 10.1.0.5. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.03.2015 10.07.2015 10.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 |
|