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

THE PERFORMANCE CAN BE SUB-OPTIMAL WHEN MAX IS USED AS A LAST HEAD
EXPRESSION IN A QUERY.

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
The query performance can be sub-optimal when it meets the
following condition;

1) It's a simple SELECT
2) It has at lest 2 MIN or MAX aggregation.
3) The MAX is the last head expression
4) The alias is used instead of the real table name.

For instance, to reproduce;

CREATE TABLE TEST  ("TEST_ID" DECIMAL(14,0) ,"TEST_DT" DATE );
CREATE ALIAS TEST_CURRENT FOR TABLE TEST;

SELECT MAX(TEST_DT), MIN(TEST_DT) FROM TEST_CURRENT WITH UR
SELECT MIN(TEST_DT), MAX(TEST_DT) FROM TEST_CURRENT WITH UR" -
Slower than above

When you run the queries above and get an execution plan, we
will find that "IS NOT NULL" is added to MAX in the first query
which is a good case, but not in the second query.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All Db2 Users                                                *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1.4.5 or later                             *
****************************************************************
Local Fix:
Rewrite the query so that the MAX is first or use the table name
instead of the Alias.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.01.2019
01.04.2020
01.04.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)