DB2 - Problem description
Problem IT23863 | Status: Closed |
APPLICATION ID IS NOT CAPTURED CORRECTLY BY ACTIVITY MONITOR, CAUSING NO INFO TO BE RETURNED WHEN RUNNING DB2EXPLN | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Simple steps to reproduce the issue: 1. Open 2 sessions to the database 2.Create activity event monitor in session 1 3. From session 1, run some sqls to be monitoried 4. In session 2, identify the query i.e. db2 "select application_handle, uow_id, activity_id, substr(stmt_text, 1, 100) from table(mon_get_activity(null,-1)) as t" 5. Pass the application_handle, uow_id, activity_id into the capture procedure: db2 "call sysproc.wlm_capture_activity_in_progress(,, ) " to capture the activity details 6. By looking at the ACTIVITYMETRICS_DBACTIVITIES, it was found that the wrong application id was captured for the activity (i.e. appl_id for connection 2 was captured instead of appl_id for connection 1). 7. Hence, when we pass this application id details obtained from Step4 above, to db2expln command, nothing was returned: i.e. db2expln -d -g -t --actevm -appid -uowid -actid | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Users on Db2 v10.5 FP9 and lower * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 v10.5 FP10 * **************************************************************** | |
Local Fix: | |
db2exfmt may be used instead. | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.01.2018 11.07.2018 11.07.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |