OA40432: HUB CRASH DURING FTO UPGRADE

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • PROBLEM DESCRIPTION:
    
    The HUB crashes eventually during the upgrade process while the
    HUB and
    MIRROR are at different versions. This is specifically known to
    occur
    while one HUB is at 6.23 while the other has been upgraded to
    6.23 FP1.
    
    
    RECREATE INSTRUCTIONS:
    
    Have both HUBs at 6.23 base level. Upgrade one of the HUBs and
    start it.
    There may be a specific order the HUBs need to be upgraded for
    this
    problem to occur, so it is conceivable that some upgrades like
    this may
    not fail.
    

Local fix

  • Do not connect the two HUBs until they are both at the same
    level of
    code.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All TEMS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: HUB MONITORING SERVER CRASH DURING      *
    *                      MIRROR MONITORING SERVER UPGRADE.       *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF.                               *
    ****************************************************************
    The hub monitoring server and mirror monitoring server are
    expected to be installed at the same level at all times.
    However, sometimes these two monitoring servers are at
    different levels during the process of upgrading the two
    servers. There are cases when some level differences between
    the hub monitoring server and mirror monitoring server are
    incompatible. When this happens, a crash can occur at one of
    the two servers if the two servers remain at different
    levels for a sufficient length of time. The time frame is
    generally expected to be a few hours.
    

Problem conclusion

  • The code has been changed to eliminate the memory growth
    that leads to the crash. It is still recommended that the
    level difference be kept to a small a time period as
    possible.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA40432

  • Reported component name

    MGMT SERVER DS

  • Reported component ID

    5608A2800

  • Reported release

    623

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-09-21

  • Closed date

    2012-10-03

  • Last modified date

    2012-11-01

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

    IV19932

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

Modules/Macros

  • KQMM     KQMPRB
    

Fix information

  • Fixed component name

    MGMT SERVER DS

  • Fixed component ID

    5608A2800

Applicable component levels

  • R623 PSY UA66835

       UP12/10/15 P F210

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Management Server for Distributed Systems on z/OS

Software version:

623

Reference #:

OA40432

Modified date:

2012-11-01

Translate my page

Machine Translation

Content navigation