DB2 FOR LUW / DB2FORLUW / B10 - DB2

When changing HostFailureDetectionTime via db2cluster command,
"db2cluster -cfs -stop -all" command should be issued to shut
down the Spectrum Scale. However, Spectrum Scale may be
automatically restarted by TSA. Depending on how long it takes
to issue the command to change HostFailureDetectionTime and/or
how long it takes to complete, it will may fail with the
following message.

# db2cluster -cfs -stop -all
All specified hosts have been stopped successfully.

# db2cluster -cm -set -option HOSTFAILUREDETECTIONTIME -value 10
Changing the host failure detection time requires the shared
file system cluster be stopped with the command 'db2cluster -cfs
-stop -all'.  Re-issue this command after the shared file system
cluster has been stopped. A diagnostic log has been saved to
'/tmp/ibm.db2.cluster.0o2h6F'.

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

A command can be issued to lock all mount resources on the
cluster; so TSA would only monitor these resources and not start
them up.
1) Lock mount resouces:  rgreq -o lock -s "Name like 'db2mnt%'"
2) db2cluster -cfs -stop -all
3) verify that Spectrum Scale is stopped on all hosts. Run the
command to change host failure detection time
4) Once complete, unlock the mount resources: rgreq -o unlock -s
"Name like 'db2mnt%'"
5) Monitor to check that TSA starts them back up or you can
start cfs : db2cluster -cfs -start -all

not known / see Local fix

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

10.12.2017
27.11.2018
27.11.2018