DB2 FOR LUW / DB2FORLUW / A10 - DB2

In db2 version v101, whenever command "db2instance", or 
"db2cluster -list -alert" are executed, trivial log entry 
"db2rocme 1 INSTANCE <instance name> <nodeID> DB2CLUSTER 
GET_HOST_INFO" will be logged in db2diag.log, which is not 
necessary. 
 
  For example, similar messages below will be logged many times 
in db2diag.log if this issue hits. 
 
2014-06-14-22.46.39.757306+540 I14803776A617        LEVEL: Event 
PID     : 31850934             TID : 1              PROC : 
db2rocme 0 [db2inst] 
INSTANCE: db2inst              NODE : 000 
HOSTNAME: db2host 
EDUID   : 1                    EDUNAME: db2rocme 0 [db2inst] 
FUNCTION: DB2 UDB, high avail services, db2rocm_main, probe:1282 
DATA #1 : SQLHA Event Recorder header data (struct 
sqlhaErPdInfo), PD_TYPE_SQLHA_ER_PDINFO, 80 bytes 
Original timestamp: 2014-06-14-22.46.39.757230271 
DATA #2 : String, 74 bytes 
/db2inst/sqllib/adm/db2rocme 1 INSTANCE db2inst 0 DB2CLUSTER 
GET_HOST_INFO 
DATA #3 : String, 5 bytes 
BEGIN 
 
2014-06-14-22.46.39.845423+540 I14804394A619        LEVEL: Event 
PID     : 31850934             TID : 1              PROC : 
db2rocme 0 [db2inst] 
INSTANCE: db2inst              NODE : 000 
HOSTNAME: db2host 
EDUID   : 1                    EDUNAME: db2rocme 0 [db2inst] 
FUNCTION: DB2 UDB, high avail services, db2rocm_main, probe:2207 
DATA #1 : SQLHA Event Recorder header data (struct 
sqlhaErPdInfo), PD_TYPE_SQLHA_ER_PDINFO, 80 bytes 
Original timestamp: 2014-06-14-22.46.39.757271841 
DATA #2 : String, 74 bytes 
/db2inst/sqllib/adm/db2rocme 1 INSTANCE db2inst 0 DB2CLUSTER 
GET_HOST_INFO 
DATA #3 : String, 7 bytes 
SUCCESS

**************************************************************** 
* USERS AFFECTED:                                              * 
* pureScale user                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 FixPack 5 or higher.             * 
****************************************************************

Problem was first fixed in DB2 UDB Version 10.1 FixPack 5

not known / see Local fix

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

30.06.2014
21.07.2015
21.07.2015