IBM Support

PI77607: ABENDS0C4 IN ALADTL1 IS POSSIBLE WHEN A MIXTURE OF COMPRESSED AND UNCOMPRESSED LOG RECORDS EXIST FOR THE SAME OBJECT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When DB2 writes a mixture of compressed and uncompressed log
    records for the same object and the ordering of the page / rid
    of the log records is such that a full row image that is
    compressed is processed first and all the partial row updates
    are not compressed and the compression dictionary in the
    current TABLESPACE can be used to decompress the objects,
    a S0C4 can occur. Under similar circumstances but different
    memory conditions an ALAA447E or ALAA440E can occur instead.
    

Local fix

  • Remove the object from the filter list and process it in Log
    Backward mode instead.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of ALA 340 or 350                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When DB2 writes a mixture of compressed *
    *                      and uncompressed log                    *
    *                      records for the same object and the     *
    *                      ordering of the page / rid              *
    *                      of the log records is such that a full  *
    *                      row image that is                       *
    *                      compressed is processed first and all   *
    *                      the partial row updates                 *
    *                      are not compressed and the compression  *
    *                      dictionary in the                       *
    *                      current TABLESPACE can be used to       *
    *                      decompress the objects,                 *
    *                      a S0C4 can occur. Under similar         *
    *                      circumstances but different             *
    *                      memory conditions an ALAA447E or        *
    *                      ALAA440E can occur instead.             *
    *                                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF                                *
    ****************************************************************
    

Problem conclusion

  • APPLY the PTF
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI77607

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    350

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-03

  • Closed date

    2017-04-25

  • Last modified date

    2017-06-08

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

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

    UI46686 UI46687

Modules/Macros

  •    ALACFREP ALACFRR  ALAETV   ALAFA    ALAGEN1
    ALALF1   ALAOBD   ALAREC   ALASTOR  ALATV    ALAUNCRE ALAXREP
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R340 PSY UI46686

       UP17/05/02 P F705

  • R350 PSY UI46687

       UP17/05/02 P F705

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.5.0"}]

Document Information

Modified date:
17 March 2021