DB2 FOR LUW / DB2FORLUW / A50 - DB2

DB2 pagecleaners may wait forever when an asynchronous I/O 
request does not return, i.e. the I/O request is stuck somewhere 
in the I/O subsystem.  While it is reasonable from a 
user/application perspective to wait forever in this state (for 
many I/O operations and system calls there is no choice), the 
DB2 behaviour will change such that DB2 pagecleaners will wait a 
maximum of 30 seconds for a batch of AIOs.  After 30 seconds 
have elapsed, the request will timeout, and the page cleaner 
will log a message to the db2diag.log as below, and return to 
wait another 30 seconds (the request cannot simply be 
abandoned). 
 
2015-05-06-17.01.57.816465-240 E104071A803          LEVEL: 
Warning (OS) 
PID     : 65536026             TID : 4628           PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000           DB   : SB 
HOSTNAME: db2host1 
EDUID   : 4628                 EDUNAME: db2pclnr (SB) 
FUNCTION: DB2 UDB, oper system services, sqloLioAIOCollect, 
probe:22 
CALLED  : OS, -, GetMultipleCompletionStatus 
OSERR   : ETIMEDOUT (78) "Connection timed out" 
MESSAGE : Incomplete IO requests and unexpected long IOCP wait 
detected.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 7.                      * 
****************************************************************

First fixed in DB2 Version 10.5 Fix Pack 7.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

04.06.2015
03.02.2016
03.02.2016