DB2 FOR LUW / DB2FORLUW / B10 - DB2

In case of member start failure, db2rocm monitor process
continues to dump the event recorders every 10 seconds even
after the db2sysc process was gone.                            


For example: the following message can be logged in db2diag.log
every 10 seconds.
----
FUNCTION: DB2 UDB, high avail services,
sqlhaEventRecorder::HaErDumpEvents, probe:314
DATA #1 : String, 56 bytes
binary event file successfully dumped ( path, recorder )
DATA #2 : String, 100 bytes
//sqllib/db2dump/DIAG0000//2018-05-10-21.11.06.4644185
17.DB2ROCM.19739.SQLHA.events.bin
DATA #3 : String, 7 bytes
DB2ROCM
----

The event recorder will be dumped in the DIAGPATH directory in
the following format :
*SQLHA.events.bin

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
****************************************************************

run db2stop force on the failed member: db2stop member  force

not known / see Local fix

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

22.06.2018
27.11.2018
27.11.2018