DB2 FOR LUW / DB2FORLUW / A10 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 2.                      * 
****************************************************************

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.

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
 

First fixed in Version 10.1 Fix Pack 2.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

16.10.2012
10.01.2013
10.01.2013