IBM Support

IT03382: 'DB2IDROP' COMMAND REMOVES NON-DB2 MANAGED RSCT CLUSTER

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When 'db2idrop' command is performed, it invokes 'db2haicu
    -delete' command as long as the 'db2haicu' utility is found.
    If there is non-DB2 managed RSCT cluster existing in the system,
    it will be removed by the 'db2haicu -delete' command. This might
    be unexpected result to some High Availability utility such as
    HACMP which also manages clusters.
    

Local fix

  • Backup up the original 'db2iutil' script, then edit it and
    comment out the lines that call 'db2haicu -delete' command.
    Here is an example of how 'db2haicu -delete' command is invoked
    in 'db2iutil' script:
    ===========================================
    drop_instance ()
    {
    
        # Check that the specified user is a valid instance name and
        # has an sqllib/bin directory in its home directory.
        if [ ${DB2INSTVER?} != ${DB2VER_UNKNOWN?} ]; then
            if [ -d ${INSTHOME?}/sqllib/bin ]; then
    
                # Clean up HA resources
                if [ -f  ${INSTHOME?}/sqllib/bin/db2haicu ]; then
                    ${DB2DIR?}/instance/db2iexec -n ${INSTNAME?}
    "${INSTHOME?}/sqllib/bin/db2haicu -delete" 1>/dev/null
    2>/dev/null
                fi
    ===========================================
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of version 9.7 on Linux, Unix and Windows          *
    * platforms.                                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Update to DB2 LUW Version 9.7 Fix Pack 10 or higher levels.  *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 LUW Version 9.7 Fix Pack 10.
    

Temporary fix

  • Backup up the original 'db2iutil' script, then edit it and
    comment out the lines that call 'db2haicu -delete' command.
    Here is an example of how 'db2haicu -delete' command is invoked
    in 'db2iutil' script:
    ===========================================
    drop_instance ()
    {
    
        # Check that the specified user is a valid instance name and
        # has an sqllib/bin directory in its home directory.
        if [ ${DB2INSTVER?} != ${DB2VER_UNKNOWN?} ]; then
            if [ -d ${INSTHOME?}/sqllib/bin ]; then
    
                # Clean up HA resources
                if [ -f  ${INSTHOME?}/sqllib/bin/db2haicu ]; then
                    ${DB2DIR?}/instance/db2iexec -n ${INSTNAME?}
    "${INSTHOME?}/sqllib/bin/db2haicu -delete" 1>/dev/null
    2>/dev/null
                fi
    ===========================================
    

Comments

APAR Information

  • APAR number

    IT03382

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-25

  • Closed date

    2014-11-10

  • Last modified date

    2014-11-10

  • 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

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IT03382

Modified date: 10 November 2014