DB2 - Problembeschreibung
Problem IC73074 | Status: Geschlossen |
CERTAIN TIME SPENT METRICS RETURNED BY MON_GET_BUFFERPOOL, MON_G ET_CONTAINER, MON_GET_TABLESPACE AND SNAPSHOTS ARE INCORRECT | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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 | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
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-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC82225 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 07.12.2010 19.12.2011 19.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |