IBM Support

IT23400: THE "DB2HAICU -DELETE" COMMAND MAY FAIL TO DELETE RESOURCES FOR THE INSTANCE IF A RESOURCE WAS INCOMPLETELY CREATED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If the db2haicu process was killed during resource creation or
    if it failed midway through resource creation, it may have left
    Db2 resources in an incompletely created state. Subsequently
    running the "db2haicu -delete" command to rollback partial
    resource creation fails with the following error reported in the
    db2diag.log:
    
    2017-11-19-04.11.35.755062+000 E36065817E852         LEVEL:
    Error
    PID     : 52940                TID : 139737789855520 PROC :
    db2haicu
    INSTANCE: db2inst1             NODE : 000
    HOSTNAME: host01
    FUNCTION: DB2 UDB, high avail services,
    sqlhaGetParentResourceGroup2, probe:300
    MESSAGE :
    ECF=0x90000552=-1879046830=ECF_SQLHA_OBJECT_DOES_NOT_EXIST
              Cluster object does not exist
    DATA #1 : String, 35 bytes
    Error during vendor call invocation
    DATA #2 : unsigned integer, 4 bytes
    18
    DATA #3 : String, 17 bytes
    db2_db2inst1_6-rs
    DATA #4 : SQLHA Cluster Session Handle,
    PD_TYPE_SQLHA_CLUSTER_HANDLE, 4120 bytes
    sqlhaClusterHandle->clusterHandle: 1
    sqlhaClusterHandle->clusterFlags: 0
    sqlhaClusterHandle->clusterErrorNum: 262152
    sqlhaClusterHandle->errorMessage: Line # : 17918---2610-407 No
    resources found.
    
    sqlhaClusterHandle->clusterCommand:
    
    The db2haicu utility should not fail in this case. It should
    proceed to delete partially created resources.
    

Local fix

  • If there is only one instance configured for HA, then the
    cluster domain can be manually deleted as follows with root
    authority:
    rmrpdomain -f <domain-name>
    
    After having manually deleted the cluster domain, the "db2haicu
    -delete" command will then successfully complete processing.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * N/A                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * First Fixed in fix pack 3 of v11.1                           *
    ****************************************************************
    

Problem conclusion

  • First Fixed in fix pack 3 of v11.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT23400

  • 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-06

  • Closed date

    2018-03-15

  • Last modified date

    2018-03-15

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

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

    IT24390

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB10 PSY

       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:
15 March 2018