IBM Support

IT31547: IN AN AUTOMATED HADR ENVIRONMENT, THERE MAY BE ERRORS IN ATTEMPTING TO DELETE MOUNT RESOURCES WHICH DO NOT EXIST

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

  • In an automated HADR/TSA environment, dropping or rebalancing a
    DMS table space container may fail and cause the Db2 instance to
    crash. Furthermore, there may be db2diag.log errors related to
    attempting to delete a mount resource, like the following shown
    below:
    
    2020-01-07-10.37.26.193350-360 E1711593E543          LEVEL:
    Error
    PID     : 601                  TID : 140736962660128 PROC :
    db2havend (db2ha)
    INSTANCE: db2inst1            NODE : 000
    HOSTNAME: xxxxxxxxxxxxxx
    FUNCTION: DB2 UDB, high avail services, db2haDeleteResource,
    probe:15033
    MESSAGE : Delete resource failed.
    DATA #1 : DB2HA Cluster Error Code,
    PD_TYPE_DB2HA_CLUSTER_ERROR_CODE, 4 bytes
    error: Cluster object does not exist
    DATA #2 : unsigned integer, 4 bytes
    Object not dumped: Address: 0x0000000000000000 Size: 4 Reason:
    Address is NULL
    
    2020-01-07-10.37.26.194047-360 E1712137E1065         LEVEL:
    Error
    PID     : 10662                TID : 140723139634944 PROC :
    db2sysc 0
    INSTANCE: db2inst1             NODE : 000            DB   : DB2
    HOSTNAME: xxxxxxxxxx
    EDUID   : 3240                 EDUNAME: db2rebal (db2inst1) 0
    FUNCTION: DB2 UDB, high avail services,
    sqlhaDeleteResourceDependency2, probe:8438
    MESSAGE :
    ECF=0x9000054C=-1879046836=ECF_SQLHA_DELETE_DEPENDENCY_FAILED
              Remove dependency failed
    DATA #1 : String, 35 bytes
    Error during vendor call invocation
    DATA #2 : String, 0 bytes
    Object not dumped: Address: 0x00007FFBE00F7A58 Size: 0 Reason:
    Zero-length data
    DATA #3 : String, 30 bytes
    db2mnt-xxxxxxxx_xxxx-rs
    DATA #4 : SQLHA Cluster Session Handle,
    PD_TYPE_SQLHA_CLUSTER_HANDLE, 4120 bytes
    sqlhaClusterHandle->clusterHandle: 1
    sqlhaClusterHandle->clusterFlags: 0
    sqlhaClusterHandle->clusterErrorNum: 0
    sqlhaClusterHandle->errorMessage: Resource handle lookup for
    resource name '_DependsOn_db2mnt-xxxxxxxx_xxxx-rs-rel' failed.
    sqlhaClusterHandle->clusterCommand:
    
    2020-01-07-10.37.26.194485-360 E1713203E717          LEVEL:
    Error
    PID     : 10662                TID : 140723139634944 PROC :
    db2sysc 0
    INSTANCE: db2inst1             NODE : 000            DB   :DB2
    HOSTNAME: xxxxxxxxxxx
    EDUID   : 3240                 EDUNAME: db2rebal (db2inst1) 0
    FUNCTION: DB2 UDB, high avail services,
    sqlhaDeleteConcurrentMountInternal, probe:12520
    MESSAGE :
    ECF=0x9000054C=-1879046836=ECF_SQLHA_DELETE_DEPENDENCY_FAILED
              Remove dependency failed
    DATA #1 : String, 43 bytes
    Failed to delete mount resource dependency.
    DATA #2 : String, 0 bytes
    Object not dumped: Address: 0x00007FFBE00F7A58 Size: 0 Reason:
    Zero-length data
    DATA #3 : String, 30 bytes
    db2mnt-xxxxxxxx_xxxx-rs
    
    
    StackTrace>
    -----FUNC-ADDR---- ------FUNCTION + OFFSET------
    0x00007FFFE8A8BD46
    _Z25ossDumpStackTraceInternalmR11OSSTrapFileiP7siginfoPvmm +
    0x0356
                    (/home/db2inst1/sqllib/lib64/libdb2osse.so.1)
    0x00007FFFE8A8B98B ossDumpStackTraceV98 + 0x002b
                    (/home/db2inst1/sqllib/lib64/libdb2osse.so.1)
    0x00007FFFE8A87B77 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm +
    0x00d7
                    (/home/db2inst1/sqllib/lib64/libdb2osse.so.1)
    0x00007FFFF02F29C7 sqlo_trce + 0x03c7
                    (/home/db2inst1/sqllib/lib64/libdb2e.so.1)
    0x00007FFFF045F451 sqloEDUCodeTrapHandler + 0x03d1
                    (/home/db2inst1/sqllib/lib64/libdb2e.so.1)
    0x0000003CC0E0F7E0 address: 0x0000003CC0E0F7E0 ; dladdress:
    0x0000003CC0E00000 ; offset in lib: 0x000000000000F7E0 ;
                    (/lib64/libpthread.so.0)
    0x0000003CC0A32495 gsignal + 0x0035
                    (/lib64/libc.so.6)
    0x0000003CC0A33C75 abort + 0x0175
                    (/lib64/libc.so.6)
    0x00007FFFF045E8F4 sqloExitEDU + 0x0174
                    (/home/db2inst1/sqllib/lib64/libdb2e.so.1)
    0x00007FFFEE608B8A _Z10sqle_panici + 0x06aa
                    (/home/db2inst1/sqllib/lib64/libdb2e.so.1)
    0x00007FFFEAF2FB19 sqlb_panic + 0x0069
                    (/home/db2inst1/sqllib/lib64/libdb2e.so.1)
    0x00007FFFEAF4763F _Z14sqlb_rebalancetPcP12SQLB_GLOBALS + 0x044f
                    (/home/db2inst1/sqllib/lib64/libdb2e.so.1)
    0x00007FFFEAF958F3 _ZN16sqbRebalancerEdu6RunEDUEv + 0x0163
    

Local fix

  • Disable automation by running the db2haicu -disable command,
    retry the failed operation and then re-enable automation by
    running the db2haicu utility on the command line and following
    the command line prompts to do so.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1.4.6 or higher                            *
    ****************************************************************
    

Problem conclusion

  • Upgrade to Db2 11.1.4.6 or higher
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT31547

  • 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

    2020-01-15

  • Closed date

    2021-03-31

  • Last modified date

    2021-03-31

  • 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 & 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:
01 April 2021