home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC72054 Status: Geschlossen

EXPLAIN OF FEDERATED QUERY INDICATES PREDICATE APPLIED TO WRONG OR
NON-EXISTENT OPERATOR

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* User of FEDERATED funtionality                               * 
**************************************************************** 
* 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.                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update the server to DB2 for Linux, Unix, Windows, Version   * 
* 9.5 Fixpack 7.                                               * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Update the server to DB2 for Linux, Unix, Windows, Version 9.5 
Fixpack 7. 
 
Once upgraded the predicate(s) show be associated with the SHIP 
operator that would have applied the predicate on the remote 
system.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC72120 IC72121 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.10.2010
12.03.2012
12.03.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.,
9.5.FP7
Problem behoben lt. FixList in der Version
9.5.0.9 FixList