IBM Support

IT23438: Running db2cluster to change hostfailuredetectiontime may fail indicating that the shared file system cluster must be stopped.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 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'.
    

Local fix

  • 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
    

Problem summary

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

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT23438

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-12-10

  • Closed date

    2018-11-27

  • Last modified date

    2018-11-27

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
27 November 2018