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 IC66160 Status: Geschlossen

DB2EXFMT OUTPUT DOES NOT SHOW TO / FROM SUBSECTION LINE ON EACH TQ
OPERATOR. THIS MAKE CORRELATING DB2EXFMT OUTPUT TO SNAPSHOTS

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
This APAR adds information about the runtime section to the 
explain_argument table for "current explain mode" settings of 
"explain",  "yes" and "reopt", and the "explain" bind options 
"yes", "all" and "reopt". With any of these explain settings, 
explain will gather information during the section code 
generation phase of optimization and add it to the explain 
tables. This makes matching up runtime section information to 
the explain generated plan much easier. The information will 
show up in the db2exfmt output under each DPF Table Queue 
operator as follows: 
 
TQNUMBER: (Runtime Table Queue number) 
1 
TQSECNFM: (Runtime Table Queue Receives From Section #) 
1 
TQSECNTO: (Runtime Table Queue Sends to Section #) 
0 
 
Take note that using the explain statement (explain plan for 
.... sql query ... ) does not generate a runtime section, and 
thus will not generate these new explain arguments.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF users of DB2 for Linux, Unix, and Windows                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* This APAR adds information about the runtime section to the  * 
*                                                              * 
* explain_argument table for "current explain mode" settings   * 
* of                                                           * 
* "explain",  "yes" and "reopt", and the "explain" bind        * 
* options                                                      * 
* "yes", "all" and "reopt". With any of these explain          * 
* settings,                                                    * 
* explain will gather information during the section code      * 
*                                                              * 
* generation phase of optimization and add it to the explain   * 
*                                                              * 
* tables. This makes matching up runtime section information   * 
* to                                                           * 
* the explain generated plan much easier. The information will * 
*                                                              * 
* show up in the db2exfmt output under each DPF Table Queue    * 
*                                                              * 
* operator as follows:                                         * 
*                                                              * 
*                                                              * 
*                                                              * 
* TQNUMBER: (Runtime Table Queue number)                       * 
*                                                              * 
* 1                                                            * 
*                                                              * 
* TQSECNFM: (Runtime Table Queue Receives From Section #)      * 
*                                                              * 
* 1                                                            * 
*                                                              * 
* TQSECNTO: (Runtime Table Queue Sends to Section #)           * 
*                                                              * 
* 0                                                            * 
*                                                              * 
*                                                              * 
*                                                              * 
* Take note that using the explain statement (explain plan for * 
*                                                              * 
* .... sql query ... ) does not generate a runtime section,    * 
* and                                                          * 
* thus will not generate these new explain arguments.          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the DB2 for Linux, Unix and Windows server to        * 
* Version 9.5, fixpack 9 or later.                             * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Upgrade the DB2 for Linux, Unix and Windows server to Version 
9.5, fixpack 9 or later.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC79495 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.02.2010
23.03.2012
23.03.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP9
Problem behoben lt. FixList in der Version
9.5.0.9 FixList