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

IMPROVE PARSING ROBUSTNESS FOR OPTIMIZER GUIDELINES

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Customers that are using optimizer guidelines - to force a 
specific query plan - sometimes have observed performance issue 
that are caused by a sub optimal access plan. The problem 
typically occurs intermittently and can be fixed by 
"re-optimizing" the query. 
 
A closer investigation will reveal that the DB2 optimizer might 
fail to correctly apply the optimizer guideline with an SQL437W 
RC=13. 
The best way to verify that you have encountered this APAR is to 
get an "explain from section" of the compiled query and to 
verify the access plan if the desired optimizer guideline was 
applied or not. 
 
This issue is caused by an incorrect parsing of the XML tag that 
is used for optimizer guideline. With this APAR we will correct 
these problems.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 2.                      * 
****************************************************************
Local Fix:
Submit the query again and ensure it get recompiled/reoptimized 
so that a new section will end up in the package cache. 
One method to accomplish this would be the "FLUSH PACKAGE CACHE 
DYNAMIC ..." statement.
available fix packs:
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
First fixed in Version 10.1 Fix Pack 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.10.2012
10.01.2013
10.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList