|
Problem IT22586
|
Status: Closed |
POOR PERFORMANCE WHEN FORCE_REPLICATED_MQT_MERGE IS SET |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
DB2 may show poor performance when following conditions are met:
- Registry variable FORCE_REPLICATED_MQT_MERGE is set
- There are replicated MQTs that can be matched
- There is EXIST/IN subquery and/or  SELECT DISTINCT
- There are joins on multiple tables or joins |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher *
**************************************************************** |
| Local Fix: |
1) Unset registry FORCE_REPLICATED_MQT_MERGE
or
2) Using registry setting DB2COMOPT=NO_DEEPKEYPU
or
2) If the query has EXIST/IN subquery, rewrite the query to
convert the EXIST/IN into join. |
| available fix packs: |
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Db2 11.1 Mod 3 Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.09.2017
19.03.2018
19.03.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
