|
Problem IC66160
|
Status: Closed |
DB2EXFMT OUTPUT DOES NOT SHOW TO / FROM SUBSECTION LINE ON EACH TQ OPERATOR. THIS MAKE CORRELATING DB2EXFMT OUTPUT TO SNAPSHOTS |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| 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. |
| Problem Summary: |
****************************************************************
* 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: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Upgrade the DB2 for Linux, Unix and Windows server to Version
9.5, fixpack 9 or later. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC79495
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.02.2010
23.03.2012
23.03.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.9
|
 |
