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

DATABASE MAY CRASH WHEN A REPLICATED MQT IS ENFORCED

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Database crashes with the following stack: 
 
_Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm + 
0x020a 
ossDumpStackTraceV98 + 0x002b 
_ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 0x0103 
sqlo_trce + 0x0407 
sqloEDUCodeTrapHandler + 0x0277 
sqloCrashOnCriticalMemoryValidationFailure + 0x0020 
sqlofmblkEx + 0x051d 
_ZN14sqlnq_ulintSet7freeMemEv + 0x0062 
_ZN15sqlnrDBConnInfo12freeMqtListsEv + 0x00bf 
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq 
lrr_cmpl_enviiPP9sqlnq_qur + 0x1eb5 
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq 
lrr_cmpl_env + 0x0021 
 
This is a rare defect where a replicated MQT enforcement is 
specified by either the registry control variable 
DB2_EXTENDED_OPTIMIZATION or by the optimization guideline.  The 
query has a high number of subquery blocks that can be matched 
to the replicated MQT and DB2 is unable to access the allocated 
memory across multiple invocations of the DB2 compiler. 
 
- The problem is introduced by v10.1 fix pack 3 APAR IC91051 
- The only fix packs that contain this problem are v10.1 fix 
pack 3 and v10.5 fix pack 3 
- v9.7 doesn't have the problem
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 fix pack 4.                             * 
****************************************************************
Local Fix:
1. Unset registry control, or take off optimization guideline 
that enforces the replicated MQT. 
2. Rewrite query statement to use the replicated MQT directly.
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 v10.1 fix pack 4.
Workaround
See local fix.
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC98085 IC98378 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.12.2013
26.06.2014
26.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList