DB2 - Problem description
Problem IC83206 | Status: Closed |
EXPLAIN OF FEDERATED QUERY INDICATES PREDICATE APPLIED TO WRONG OR NON-EXISTENT OPERATOR | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
A predicate may not show up in the explain output (db2exfmt, Visual Explain, Optimum Query Tuner), or it may be associated with the wrong operator, when a query against a remote table is explained, and that query includes a predicate against that remote table. You are experiencing this problem if the following query returns a non-zero count: select count(*) from explain_predicate where operator_id > (select max(operator_id) from explain_operator) You are also experiencing this problem if a local predicate is applied to an operator that does not contain the columns associated with that predicate. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users of DB2 v10.1 who use the EXPLAIN facility * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade the DB2 Linux Unix and Windows server to v10.1 fix * * pack 1 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
This fix is in DB2 Linux Unix and Windows v10.1 fix pack 1. Upgrade to this version in order for the predicates to show as being applied at or below the SHIP operator and the Nickname Objects accessed by that SHIP operator. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.05.2012 02.11.2012 02.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |