|
Problem IC84184
|
Status: Closed |
DB2 MAY ABEND WHEN THERE ARE MULTIPLE REPLICATED MQT AND FORCE_REPLICATED_MQT_MERGE IS SET |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When the following conditions are all met, compiling a query or
modifying statement may trap with stack:
sqlnq_qtboprparent::op
sqlnq_mch::is_maximal
sqlnq_som::compute_matchinfo_opt
sqlnr_compute_matchinfo
sqlnr_optprep
sqlnr_optprep_action
(1) There are at least two replicated MQT (Materialized Query
Table) and at least one non-replicated optimizer MQT or
statistical view. An optimizer MQT is such MQT whose definition
is simply "SELECT <expression list> FROM <one or more base
tables> WHERE <predicates>".
(2) Registry variable DB2_EXTENDED_OPTIMIZATION includes flag
FORCE_REPLICATED_MQT_MERGE.
(3) The query statement itself contains multiple subqueries, or
the modifying statement's target table has multiple enforced
checking constraint defined. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* N/A *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10 Fix Pack 1. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Fixed on DB2 Version 10 Fix Pack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.06.2012
28.12.2012
28.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
