home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC77113 Status: Closed

QUERIES NOT ROUTED TO MQTS DUE TO DEFECTIVE MQT OR STATVIEW

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 compiler attempts to match query with all of the MQT and 
statview (statistical view) that depends on query referenced 
base table or nickname.  All of the MQT and statview are 
supposed to be present in catalog table sysibm.systables. In 
case an MQT or statview is attempted to match to query but it 
has no catalog row, the query compilation used to disable MQT 
matching.   The following message is displayed in the db2exfmt 
extended diagnostic for the query: 
 
Diagnostic Details: 
     EXP0080W  The current usage of the statement or the 
     statement containing update, delete or insert or 
     constructs like sampling limits MQT matching. 
 
With this fix, the remaining MQT and statview are still matched 
to the query, and the unexpected MQT or statview is ignored by 
matching and a corresponding EXP0058W diagnostic message will 
capture its schema and name.
Problem Summary:
DB2 compiler attempts to match query with all of the MQT and 
statview (statistical view) that depends on query referenced 
base table or nickname.  All of the MQT and statview are 
supposed to be present in catalog table sysibm.systables. In 
case an MQT or statview is attempted to match to query but it 
has no catalog row, the query compilation used to disable MQT 
matching.  The following message is displayed in the db2exfmt 
extended diagnostic for the query: 
 
Diagnostic Details: 
    EXP0080W  The current usage of the statement or the 
    statement containing update, delete or insert or 
    constructs like sampling limits MQT matching. 
 
With this fix, the remaining MQT and statview are still matched 
to the query, and the unexpected MQT or statview is ignored by 
matching and a corresponding EXP0058W diagnostic message will 
capture its schema and name.
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.7 Fix Pack 5
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC82500 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.06.2011
09.12.2011
09.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList