IBM Support

LI75550: MAKE DB2HAICU MORE ROBUST AND HAVE IT REMOVE ORPHAN RESOURCES DU RING DB2HAICU -DELETE IF THEY STILL EXIST.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If you use TSA commands to administer a HADR cluster with
    CT_MANGEMENT_SCOPE not set to 2, you could risk creating orphan
    resources which may cause db2haicu to fail.
    .
    For example,
    On HostA -
    rmrsrc -s "Name like 'db2_<instance>%' " IBM.Application
    rmrsrc -s "Name like '%' " IBM.Test
    rmrg -s "Name like 'db2_<instance>%' "
    .
    This will remove resource groups on both HostA and HostB, but
    only children resources on HostA are removed.
    .
    As a result "db2haicu -delete" will fail as it currently does
    not handle orphan resources.
    .
    The purpose of this APAR is to make db2haicu more robust and
    have it remove orphan resources for the instance in question,
    assuming the orphan  was originally created by db2haicu.
    

Local fix

  • In general, you can't delete a resource which is Online (as the
    message suggests). You should stop the instances on each
    server and then remove the resources.
    Or, you can add the Force=1 option to each remove command. For
    completeness, here are the modified instructions with the
    Force=1 option :
    As root user (from either node) :
    export CT_MANAGEMENT_SCOPE=2        <== this should be added to
    your user profile on both nodes
    rmrsrc -s "Name like '<instance>' " IBM.Application  Force=1
    rmrsrc -s "Name like '%' " IBM.Test  Force=1
    rmrg -s "Name like '<instance>' "
    

Problem summary

  • If you use TSA commands to administer a HADR cluster with
    CT_MANGEMENT_SCOPE not set to 2, you could risk creating orphan
    resources which may cause db2haicu to fail.
    .
    For example,
    On HostA -
    rmrsrc -s "Name like 'db2_<instance>%' " IBM.Application
    rmrsrc -s "Name like '%' " IBM.Test
    rmrg -s "Name like 'db2_<instance>%' "
    .
    This will remove resource groups on both HostA and HostB, but
    only children resources on HostA are removed.
    .
    As a result "db2haicu -delete" will fail as it currently does
    not handle orphan resources.
    .
    The purpose of this APAR is to make db2haicu more robust and
    have it remove orphan resources for the instance in question,
    assuming the orphan  was originally created by db2haicu.
    

Problem conclusion

  • apar li75550
    fixed >= v95 fpk7
    

Temporary fix

  • In general, you can't delete a resource which is Online (as the
    message suggests). You should stop the instances on each
    server and then remove the resources.
    Or, you can add the Force=1 option to each remove command. For
    completeness, here are the modified instructions with the
    Force=1 option :
    As root user (from either node) :
    export CT_MANAGEMENT_SCOPE=2        <== this should be added to
    your user profile on both nodes
    rmrsrc -s "Name like '<instance>' " IBM.Application  Force=1
    rmrsrc -s "Name like '%' " IBM.Test  Force=1
    rmrg -s "Name like '<instance>' "
    

Comments

APAR Information

  • APAR number

    LI75550

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-07-27

  • Closed date

    2010-12-20

  • Last modified date

    2010-12-20

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

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

    IC70219

Modules/Macros

  • ENGN_HA
    

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • R950 PSN

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

Document Information

Modified date:
20 December 2010