DB2 - Problem description
Problem IC97866 | Status: Closed |
Running db2advis to recommend MQT can cause DB2 to trap when the input query contains sub-queries that meet certain conditions | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Running db2advis to recommend MQT can cause DB2 to trap when the input query meets all of the following conditions: - the query contains a sub-query predicate that references columns from only one table. - the sub-query contains local predicates. - for exists or not-exists sub-query, the select clause of the sub-query contains only constants or parameter markers. - the query has aggregate functions. For example: SELECT MAX(T1_C1) FROM T1 WHERE CAST(? AS INT) <= ALL(SELECT T2_C1 FROM T2 WHERE T2_C1 > 2 ) SELECT MIN(T1_C1) FROM T1 WHERE NOT EXISTS (SELECT 134, CAST(? as INT) FROM T2 WHERE T2_C1 > 2 ) The stack trace-back can contain the following functions: sqlng_build_SQZO_obj sqlng_process_groupby_op sqlngProcessLolepop sqlng_process_sort_op sqlngProcessLolepop sqlng_build_thread | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 4 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 10.5 Fix Pack 4 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.11.2013 08.09.2014 08.09.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.4 |