IBM Support

IV56654: TGROUPI DISCREPANCIES IN FTO

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ********************** START OF APAR OPEN TEMPLATE
    *********************
    * Please open an apar with the following severity and
    information:     *
    *
           *
    APAR Type:            Field
    Approver Initials:    RB
    Severity:             3
    Reported Release:     623
    Compid:               5724C04MS Tivoli Enterprise Management
    Server
    
    PROBLEM DESCRIPTION:
    Deleting a situation in an FTO environment will result in
    orphaned group member records in the TGROUPI table at the
    MIRROR. It is possible under the right circumstances for these
    records to make their way back to the acting HUB.
    
    RECREATE INSTRUCTIONS:
    In an FTO environment with the HUB and MIRROR running:
    - Create a situation
    - add the situation to a situation group.
    - Verify the resulting group member record exists in the
    TGROUPI table at the acting HUB and at the MIRROR.
    - Delete the situation at the acting HUB
    - Check again for the group member record at the acting HUB and
    the MIRROR. It will be gone from the acting HUB but still found
    at the MIRROR.
    
    LOCAL FIX:
    The group member record at the MIRROR will need to be manually
    deleted.
    
    *********************** END OF APAR OPEN TEMPLATE
    **********************
    

Local fix

Problem summary

  • Group member discrepancies between hub monitoring server and
    mirror monitoring server.
    
    
    Contents of the group member table can get out of sync between
    the hub monitoring server and the mirror monitoring server. The
    problem occurs when deleting a situation that is assigned to one
    or more groups. This leaves orphaned group members at the mirror
    monitoring server. The orphaned group member records can make
    their way back to the hub monitoring server during fail over
    operations. The orphaned group members are typically harmless,
    though can become relevant if the deleted situation is
    recreated.
    

Problem conclusion

  • The product has been modified to remove the group members at the
     mirror monitoring server when a situation is deleted.
    
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
      | fix pack | 6.3.0-TIV-ITM-FP0003
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV56654

  • Reported component name

    TEMS

  • Reported component ID

    5724C04MS

  • Reported release

    623

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-03-13

  • Closed date

    2014-07-22

  • Last modified date

    2014-08-08

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

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

    OA45674

Fix information

  • Fixed component name

    TEMS

  • Fixed component ID

    5724C04MS

Applicable component levels

  • R630 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"623"}]

Document Information

Modified date:
30 December 2022