DB2 - Problem description
Problem IC91812 | Status: Closed |
QUERY CONTAINING EXISTS SUBQUERY AND FETCH FIRST N ROWS CLAUSE MIGHT PRODUCE INCORRECT RESULTS | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
Under certain scenario, DB2 might produce incorrect results if the following conditions are true: 1. The query contains an exists subquery 2. The subquery has a fetch first n rows clause in the outer most subselect 3. There is either a LOB column or a total column column width > 32K in the query output list. Eg.: select P.lob from P where exists (select 1 from SQ where SQ.c1 = P.c1 fetch first 1 rows only); | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.1 fixpack 3 * **************************************************************** | |
Local Fix: | |
1. Remove fetch first n rows clause 2. Add order by clause to the subquery. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Fixed in DB2 version 10.1 fixpack 3 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC95267 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.04.2013 11.11.2013 11.11.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |