IBM Support

IT24735: Member failback may fail with SQL1072C after rmcd process failure on member's home host.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The issue can occur if Member is in restart light mode on
    another host because of a failure of the rmcd daemon.  When a
    member tries to failback to its home host, the start of the
    member may fail due to leftover IPC resources on the host.
    
    
    If the issue is hit, the following error will be seen in
    db2diag.log:
    
    FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:5560
    MESSAGE : ZRC=0xFFFFFBD0=-1072
    SQL1072C The request failed because the database manager
    resources are in an inconsistent state. The database manager
    might have been incorrectly terminated, or another application
    might be using system resources in a way that conflicts with the
    use of system resources by the database manager.
    
    DATA #1 : <preformatted>
    RCOM Cleanup done but still got resource error
    
    This means that the start of the member has failed because of
    leftover IPC resources on its home host even after the cleanup.
    

Local fix

  • Before member can start again on its home host, the leftover IPC
    resources need to be manually cleaned up on that host.
    
    To start the member on its home host, run:
    ipclean -a
    db2start member <member_id>
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * pureScale user                                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 Version 11.1 fixpack 4 or later.              *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 Version 11.1 fixpack 4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT24735

  • 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

    2018-04-16

  • Closed date

    2018-12-23

  • Last modified date

    2021-07-30

  • 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

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1"}]

Document Information

Modified date:
31 July 2021