|
Problem IC73074
|
Status: Closed |
CERTAIN TIME SPENT METRICS RETURNED BY MON_GET_BUFFERPOOL, MON_G ET_CONTAINER, MON_GET_TABLESPACE AND SNAPSHOTS ARE INCORRECT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The following metrics returned by MON_GET_BUFFERPOOL and the
corresponding elements from snapshot monitor may be wrongly
reported --
POOL_READ_TIME
POOL_WRITE_TIME
DIRECT_READ_TIME
DIRECT_WRITE_TIME
LOCK_WAIT_TIME_HIGH_WATERMARK (in statistics event monitor)
Also, the following metrics reported by snapshot monitor and
snapshot functions could be double the value of that reported by
the new monitoring functions, namely, MON_GET_CONTAINER and
MON_GET_TABLESPACE --
DIRECT_READ_TIME
DIRECT_WRITE_TIME |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users running DB2 v9.7 FP4 or earlier. *
****************************************************************
* PROBLEM DESCRIPTION: *
* The following metrics returned by MON_GET_BUFFERPOOL and the *
* *
* corresponding elements from snapshot monitor may be wrongly *
* *
* reported -- *
* *
* *
* *
* POOL_READ_TIME *
* *
* POOL_WRITE_TIME *
* *
* DIRECT_READ_TIME *
* *
* DIRECT_WRITE_TIME *
* *
* LOCK_WAIT_TIME_HIGH_WATERMARK (in statistics event monitor) *
* *
* *
* *
* Also, the following metrics reported by snapshot monitor and *
* *
* snapshot functions could be double the value of that *
* reported by *
* the new monitoring functions, namely, MON_GET_CONTAINER and *
* *
* MON_GET_TABLESPACE -- *
* *
* *
* *
* DIRECT_READ_TIME *
* *
* DIRECT_WRITE_TIME *
****************************************************************
* RECOMMENDATION: *
* Recommended to upgrade to DB2 for LUW v97fp5. *
**************************************************************** |
| Local Fix: |
For the following metrics reported by MON_GET_BUFFERPOOL, divide
the values by 2 before using them --
POOL_READ_TIME
POOL_WRITE_TIME
DIRECT_READ_TIME
DIRECT_WRITE_TIME
LOCK_WAIT_TIME_HIGH_WATERMARK (in statistics event monitor)
For the following metrics reported by snapshots, consider either
the values for the same metrics reported by MON_GET_CONTAINER
and MON_GET_TABLESPACE, or divide the values by 2 before using
them --
DIRECT_READ_TIME
DIRECT_WRITE_TIME |
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
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 |
The fix for this problem will be available from v97fp5 onwards. |
| Workaround |
For the following metrics reported by MON_GET_BUFFERPOOL,
divide
the values by 2 before using them --
POOL_READ_TIME
POOL_WRITE_TIME
DIRECT_READ_TIME
DIRECT_WRITE_TIME
LOCK_WAIT_TIME_HIGH_WATERMARK (in statistics event monitor)
For the following metrics reported by snapshots, consider
either
the values for the same metrics reported by MON_GET_CONTAINER
and MON_GET_TABLESPACE, or divide the values by 2 before using
them --
DIRECT_READ_TIME
DIRECT_WRITE_TIME |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC82225
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.12.2010
19.12.2011
19.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
