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 IT17295 Status: Closed

Queries with a MAX scalar function over a nullable column may not be routed
to an MQT

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Queries with a MAX scalar function over a nullable column may 
not be routed to an MQT. 
 
A query of the form: 
           select max(col) from T ?     , where col is a 
nullable column 
may not be routed to a materialized query table (M) defined on 
base table T. 
 
The following will be observed in the diagnostic section of the 
access plan, where T is the base table of M: 
 
Diagnostic Details: 	EXP0062W  The following MQT or statistical 
view was 
			not eligible because one or more columns or 
			expressions referenced in the query were not found 
			in the MQT: <schema>.?M?.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 6                               * 
****************************************************************
Local Fix:
Modify the column referenced in the MAX function parameter to an 
expression that returns the same value as the column. 
 
For example, if col is a column of a numeric data type, 
modifying max(col) to max(col+0).
Solution
First fixed in DB2 10.1 Fix Pack 6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.09.2016
02.03.2017
02.03.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)