DB2 FOR LUW / DB2FORLUW / 980 - DB2

There can be situations where a guest member executing restart 
light may encounter a time out and the process ended. 
Symptoms of this situation are the following entries in the 
db2diag.log after the member process was ended: 
 
db2rocme was faced "Action timed out". 
2012-01-25-00.00.14.915820+540 I135030A1996         LEVEL: 
Warning 
PID     : 24379508             TID  : 1             PROC : 
db2rocme 2 [db2inst1] 
INSTANCE: db2inst1              NODE : 002 
HOSTNAME: test3c 
EDUID   : 1                    EDUNAME: db2rocme 2 [db2inst1] 
FUNCTION: DB2 UDB, fast comm manager, 
sqkfNodeManager::queryClusterStateIsDrained, probe:1641 
RETCODE : ZRC=0x87000057=-2030043049=SQLZ_RC_TIMEOUT "Action 
timed out" 
          DIA8578C A timeout occurred while waiting on a 
semaphore. 
DATA #1 : ROCM DB2 notification query control block, 
PD_TYPE_ROCM_QUERY_CM_NOTIF_CB, 32 bytes

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.8 fixpack 5.                    * 
****************************************************************

Problem was first fixed in DB2 UDB Version 9.8 Fixpack 5.

keiner bekannt / siehe Local-Fix

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

13.02.2012
20.06.2012
20.06.2012

9.8.FP5