IBM Support

IT25601: "DB2CLUSTER -CM -ENTER -MAINTENANCE" COMMAND FAILS IF RUN ON A TIEBREAKER HOST IN GDPC ENVIRONMENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • In a GDPC pureScale environment, the following error may be
    encountered when attempting to enter maintenance mode on the
    tiebreaker host:
    
    $ /opt/IBM/DB2/V11.1.3/bin/db2cluster -cm -enter -maintenance
    DBT8066E Unable to enter maintenance mode on host "TBhostA".
    Reason code = "3".
    A diagnostic log has been saved to
    '/tmp/ibm.db2.cluster.qyFz13s.
    

Local fix

  • In order to workaround this issue, RSCT can be stopped via
    native RSCT commands, e.g. the "stoprpnode TBhostA" command can
    be used to stop RSCT on the tiebreaker host. In order to then
    exit maintenance mode, RSCT can be started back up on the host
    via the "startrpnode TBhostA" command. Note that the startrpnode
    command must be issued from another host in the cluster.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * pureScale GDPC users                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 version 11.1 Mod pack 4 Fix pack 4            *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT25601

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-07-06

  • Closed date

    2018-12-03

  • Last modified date

    2018-12-03

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

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

Fix information

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:
03 December 2018