DB2 FOR LUW / DB2FORLUW / A50 - DB2

When running "db2cluster -cfs -exit -maintenance" command after
"db2cluster -cm -exit -maintenance" command, it may fail with
return code 2. The db2cluster error log shows as follows:

2017-07-21-01.59.07.362335+540 I1571A329            LEVEL: Info
PID     : 12845128             TID : 1              PROC :
db2cluster
INSTANCE:                      NODE : 000
HOSTNAME: pshost1
EDUID   : 1
FUNCTION: , , , probe:2595
DATA #1 : String, 58 bytes
/opt/IBM/db2/V10.5/bin/db2cluster -cfs -exit -maintenance

2017-07-21-02.07.05.182009+540 I1901A459            LEVEL:
Severe
PID     : 12845128             TID : 1              PROC :
db2cluster
INSTANCE:                      NODE : 000
HOSTNAME: pshost1
EDUID   : 1
FUNCTION: DB2 UDB, high avail services,
sqlhaCFSCallFunctionDirect, probe:114
MESSAGE : ECF=0x9000052E=-1879046866=ECF_SQLHA_FAILED
          SQLHA API call error
DATA #1 : String, 22 bytes
DB2CFS function error.
DATA #2 : signed integer, 4 bytes
27

The mmstartup is invoked asynchronously after "db2cluster -cm
-exit -maintenance" command. Some GPFS commands invoked in
"db2cluster -cfs -exit -maintenance" may fail due to a lock held
by the mmstartup command depending on timing.

****************************************************************
* USERS AFFECTED:                                              *
* pureScale user                                               *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 10.5 Fix Pack 10 or higher                    *
****************************************************************

Check if GPFS state is active by mmgetstate command before
running "db2cluster -cfs -exit -maintenance"

not known / see Local fix

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

28.07.2017
18.07.2018
18.07.2018