DB2 - Problem description
Problem IT36821 | Status: Closed |
SET EVENT MONITOR STATE STATEMENTS MAY BE INCORRECTLY QUEUED BY THE ADAPTIVE WORKLOAD MANAGER | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
The adaptive workload manager incorrectly intercepts SET EVENT MONITOR statements. Under periods of heavy resource contention these statements may end up getting queued. This can lead to errors or timeouts from applications submitting these statements. SET EVENT MONITOR statements are light weight monitor statements and should always bypass the adaptive workload manager control. You can detect if you are running into this apar by monitoring queued statements using either the MON_GET_ACTIVITY interface (for currently executing statements) or an activity event monitor (for historical statement execution) and looking at the wlm_queue_time_total monitor element for SET EVENT MONITOR statements. If you see a non-zero queue time and the adaptive workload manager is enabled (wlm_admission_ctrl db config parameter is set to yes) this apar is applicable. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Any users who have the adaptive workload manager enabled * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to the latest mod pack. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Any users who have the adaptive workload manager enabled * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to the latest mod pack. * **************************************************************** | |
Comment | |
Problem was first fixed in DB2 UDB Version 11.5 mod pack 6 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.05.2021 11.06.2021 11.06.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |