IBM Support

IT25138: THE "DB2CLUSTER -CM -ENTER -MAINTENANCE COMMAND" MAY FAIL DUE TOTSA RESOURCES PROBLEM

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Once user executes "db2cluster -cm -enter -maintenance" command,
    it may return error:
    
    -bash-4.2$ sudo /opt/IBM/db2/V10.5/FP9/bin/db2cluster -cm -enter
    -maintenance -debug
    Unable to enter maintenance mode on the local host.
    A diagnostic log has been saved to
    '/tmp/ibm.db2.cluster.NMNqaa'..
    
    
    In the diagnostic file one can observe message similar to
    following:
    
    2018-05-14-07.56.58.130870-300 E14673A1008          LEVEL: Error
    PID     : 4718904              TID : 1              PROC :
    db2cluster
    INSTANCE: db2inst1             NODE : 000
    HOSTNAME: node01
    EDUID   : 1
    FUNCTION: <0>, <0>, <0>, probe:2681
    RETCODE : ECF=0x9000053B=-1879046853=ECF_SQLHA_STOP_NODE_FAILED
              Node stop failed
    DATA #1 : String, 66 bytes
    libsqlha: sqlhaOfflineDomainNode() call error from wrapper
    library
    DATA #2 : String, 506 bytes
    Line # : 19048---2632-110 The operation was rejected by one or
    more nodes, probably because one or more resources are online or
    there was an error encountered in determining if any resources
    are online.
    node01: 2632-054 The requested operation failed due to the
    rejection from the resource class IBM.CHARMControl.
    Message returned from the resource class: 2621-793 Node "node01"
    cannot be made offline. System Automation Manager reports that
    there are resources online on this node..
    ; FFDC ID:
    DATA #3 : signed integer, 4 bytes
    98349
    

Local fix

  • db2stop member/cf <member/cf number>;
    db2stop instance on <hostname>;
    touch /var/db2/.db2_maintenance_`hostname -s`;
    -------------- wait for all mount resources on that host to go
    to "failed offline" state;
    db2cluster -cm -enter -maintenance;
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 m4fp4 or later                           *
    ****************************************************************
    

Problem conclusion

  • Upgrade to Db2 11.1 m4fp4 or later
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT25138

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-05-23

  • Closed date

    2018-11-29

  • Last modified date

    2018-11-29

  • 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

[{"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":"10.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
29 November 2018