IBM Support

PI08810: VARIOUS ISSUES AFTER QUIESCING A SUBSYSTEM IN A DATA SHARING ENVIRONMENT WHILE RUNNING IN CONTINUOUS MODE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When running in continuous mode, the last processed LOGPOINTs of
    each of the subsystems is stored in a file so Log Analysis Tool
    can pick up where it last ended. If a subsystem is QUIESCED, the
    last processed LOGPOINT for that subsystem begins to age since
    no new log records are processed. This aging leads to various
    issues such as DB2 archive logs being unnecessarily recalled
    from HSM, an internal array becoming full and not allowing
    further processing, or in some very obscure cases duplicate data
    being processed.
    

Local fix

  • Manually delete the old LOGPOINT in the continuous mode file
    with the assistance of product support.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis Tool.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: When running in continuous mode, the    *
    *                      last processed LOGPOINTs of each of     *
    *                      the subsystems is stored in a file so   *
    *                      Log Analysis Tool can pick up where it  *
    *                      last ended. If a subsystem is QUIESCED, *
    *                      the last processed LOGPOINT for that    *
    *                      subsystem begins to age since           *
    *                      no new log records are processed. This  *
    *                      aging leads to various issues such as   *
    *                      DB2 archive logs being unnecessarily    *
    *                      recalled from HSM, an internal array    *
    *                      becoming full and not allowing          *
    *                      further processing, or in some very     *
    *                      obscure cases duplicate data            *
    *                      being processed.                        *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI08810

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    330

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-12-31

  • Closed date

    2014-01-28

  • Last modified date

    2014-03-03

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

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

    UI14562 UI14563

Modules/Macros

  •    ALAFRMTR ALAGEND  ALAIN4X  ALAIN4XR ALASUBG
    ALAUNCRE
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R330 PSY UI14562

       UP14/02/06 P F402

  • R340 PSY UI14563

       UP14/02/06 P F402

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.3.0"}]

Document Information

Modified date:
18 March 2021