home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC90979 Status: Closed

NEGATIVE NUMBER IS RETURNED FOR PROCESSING TIME OR WAIT TIME COUNTER FROM
MON_GET TABLE FUNCTION

product:
DB2 FOR LUW / DB2FORLUW / 970 - 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 
diaglog_writes_total 
direct_read_reqs 
direct_write_reqs 
ida_recvs_total 
ida_sends_total 
ipc_recvs_total 
ipc_sends_total 
lock_waits 
log_disk_waits_total 
num_log_buffer_full 
tcpip_recvs_total 
tcpip_sends_total 
total_app_commits 
total_app_rollbacks 
total_app_section_executions 
total_compilations 
total_implicit_compilations 
total_loads 
total_reorgs 
total_runstats 
total_section_sorts 
wlm_queue_assignments_total
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users on DB2 V97 FP8 and lower                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V97 FP9                                       * 
****************************************************************
Local Fix:
No Local Fix
available fix packs:
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 V97 FP9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC91440 IC95234 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.03.2013
17.12.2013
17.12.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.9 FixList
9.7.0.9 FixList