|
Problem IT28018
|
Status: Closed |
UOW_ID of an unit of work is not collected for UOWTOTALTIME threshold violation
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
The UOW_ID of an unit of work is not collected for UOWTOTALTIME
threshold violation, when all of the related activities finish
before the threshold, except the connection itself exceeds.
The case with UOW_ID=0 can be simulated, by creating event
monitors and uow threshold and launching a unit of work which
exceeds the threshold_value.
If all statements of that unit of work have been executed
before the threshold_value and if the commit operation will be
performed after the threshold_value , then uow_id=0. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.02.2019
06.07.2020
06.07.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
