DB2 FOR LUW / DB2FORLUW / A10 - DB2

pool_async_write_time is currently reporting an estimate of how 
long pagecleaners have waited for any number of I/Os to 
complete.  However, documentation also suggests it is the 
acccumulation of time spent for each I/O to complete.  A formula 
is provided where it is suggested that average async write time 
can be determined by dividing asynchronous write time by the 
number of asynchronous writes, which is incorrect given the 
current information being returned.  Pagecleaners use 
asynchronous I/O, which involves submitting I/Os in batches, and 
it becomes more difficult to apportion time to specific I/Os (we 
may wait for the longest one in a batch to be complete before 
processing any of the completed I/Os).  Regardless, a more 
accurate measure of I/O performance would be provided if the 
end-to-end times of each I/O were accumulated.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 systems are affected                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5                       * 
****************************************************************

use operating system tools to monitor write performance

Problem first fixed in DB2 Version 10.1 Fix Pack 5

see Local Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

01.12.2014
23.07.2015
23.07.2015