|
Problem IC91440
|
Status: Closed |
NEGATIVE NUMBER IS RETURNED FOR PROCESSING TIME OR WAIT TIME COUNTER FROM MON_GET TABLE FUNCTION |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
On highly OLTP environments it is possible for a counter for the
number of processing times or wait times to become negative.
For example, the following query could return a negative value
on highly OLTP environments:
db2 "select TOTAL_APP_SECTION_EXECUTIONS from
table(mon_get_workload(NULL,-1)) as T where workload_name like
'%USER%' "
TOTAL_APP_SECTION_EXECUTIONS
----------------------------
-7058505513
This can occur with the following table functions:
MON_GET_CONNECTION
MON_GET_PKG_CACHE_STMT
MON_GET_SERVICE_SUBCLASS
MON_GET_UNIT_OF_WORK
MON_GET_WORKLOAD
When the counter is returned by a table function that returns an
XML document, the counter is defined to be a
"xs:nonNegativeInteger". In this case the value can become a
massive value rather than a negative value. For example, the
IPC_RECVS_TOTAL counter reported by MON_GET_CONNECTION_DETAILS
is "18446744072615334103".
This can occur with the following table functions:
MON_GET_ACTIVITY_DETAILS
MON_GET_CONNECTION_DETAILS
MON_GET_PKG_CACHE_STMT_DETAILS
MON_GET_SERVICE_SUBCLASS_DETAILS
MON_GET_UNIT_OF_WORK_DETAILS
MON_GET_WORKLOAD_DETAILS
The following counters are susceptible to this issue:
agent_waits_total
audit_file_writes_total
audit_subsystem_waits_total
comm_exit_waits
diaglog_writes_total
direct_read_reqs
direct_write_reqs
evmon_waits_total
ida_recvs_total
ida_sends_total
ipc_recvs_total
ipc_sends_total
lock_waits
log_disk_waits_total
num_log_buffer_full
prefetch_waits
tcpip_recvs_total
tcpip_sends_total
total_app_commits
total_app_rollbacks
total_app_section_executions
total_compilations
total_connect_authentications
total_connect_requests
total_extended_latch_waits
total_implicit_compilations
total_loads
total_reorgs
total_runstats
total_section_sorts
total_stats_fabrications
total_sync_runstats
wlm_queue_assignments_total |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users on DB2 v101 FP2 and lower *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V101 FP3 *
**************************************************************** |
| Local Fix: |
No Local Fix |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First Fixed in DB2 v101 FP3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.04.2013
10.03.2014
10.03.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
