home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC82902 Status: Geschlossen

IMPROVE PARSING ROBUSTNESS FOR OPTIMIZER GUIDELINES

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 7.                       * 
****************************************************************
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.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in Version 9.7 Fix Pack 7.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC87286 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.04.2012
25.10.2012
25.10.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP7
Problem behoben lt. FixList in der Version
9.7.0.7 FixList