DB2 - Problem description
Problem IT08285 | Status: Closed |
IN DB2PD -APINFO OUTPUT, ADD A FIELD THAT REPORTS THE CURRENT RUNTIME DEGREE OF A QUERY. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Currently, the "Effective degree" field reflects the compilation degree of parallelism, not runtime degree. The title of Effective degree easily leads to the expectation that it reflects the degree of parallelism actually in use for the running of the statement. This APAR is to fix the db2pd -apinfo output that will update the description of Number of Agents to something more indicative of what is actually being reported, add a field that reports the actual runtime degree alongside of Effective degree, and add a field that will report the Active Agents from existing monitors. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * upgrade to 10.5 fp7 * **************************************************************** | |
Local Fix: | |
Use the mon_get_activity() table function to monitor the in effect query parallelism, specifically the QUERY_ACTUAL_DEGREE field. For example: $ db2 "select num_agents,agents_top,effective_query_degree,query_actual_degree from table(mon_get_activity(616,-1)) t" NUM_AGENTS AGENTS_TOP EFFECTIVE_QUERY_DEGREE QUERY_ACTUAL_DEGREE -------------------- -------------------- ---------------------- ------------------- 3 3 12 2 1 record(s) selected. This shows the actual parallelism applied to the query. | |
Solution | |
first fixed in 10.5 fp7 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.04.2015 22.01.2016 22.01.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.7 |