IBM Support

PM67662: RESTART STANDBY SERVER CAUSED THE SERVER GO DISCONNECTED STATE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • TPC-R standby server was re-started. It was synchronized before
    the restart but when it came back up it was in disconnected
    state, rather than in "disconnect consistent" state, which
    is the proper state if it was synchronized before the restart.
    

Local fix

Problem summary

  • Oncec synchronized the High availability between the active and
    the standby server went "disconnected" state instead of
    "disconnected consistent" thus possibly misleading users that
    the a takeover would now have stale data.
    

Problem conclusion

  • After restart, both active and standby server are in "disconnect
    consistent" state.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM67662

  • Reported component name

    TPC FOR REPL Z/

  • Reported component ID

    5608TRMZ0

  • Reported release

    42B

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-26

  • Closed date

    2012-07-30

  • Last modified date

    2012-07-30

  • 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

    TPC FOR REPL Z/

  • Fixed component ID

    5608TRMZ0

Applicable component levels

  • R42X PSY

       UP

  • R42Y PSY

       UP

  • R51B PSY

       UP

  • R51Y PSY

       UP

[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSMN28","label":"Tivoli Storage Productivity Center for Replication"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"42B"}]

Document Information

Modified date:
17 November 2021