|
Problem IT22593
|
Status: Closed |
WLM STMT THRESHOLD DO NOT STOP EXECUTION WHEN SPECIFIC SQL IS RUN. |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
Creating an SQL Statement thresholds may stop being active after
an instance/database restart. In order to get it working again
you would need to drop/create the threadhold again.
Can check the active threads hold by using the following:
db2 "SELECT t.application_handle, t.uow_id, t.activity_id,
t.ACTIVITYTOTALTIME_THRESHOLD_ID,
ACTIVITYTOTALTIME_THRESHOLD_VALUE,
ACTIVITYTOTALTIME_THRESHOLD_VIOLATED, VARCHAR(t.stmt_text, 256)
as stmt_text FROM table(MON_GET_ACTIVITY(NULL, -1)) as t "
db2 "SELECT THRESHOLDNAME, THRESHOLDID FROM SYSCAT.THRESHOLDS" |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* 999 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* It is a code issue and it has been fixed in 105fp10. *
**************************************************************** |
| Local Fix: |
Drop/Create the SQL Threshold. |
| available fix packs: |
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.09.2017
15.03.2018
15.03.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
