IBM Support

PK53299: POSSIBLE ALAA447E, ALAA440E MESSAGE WHEN MANY UPDATES TO SAME ROW

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During merge processing (aka, LOG APPLY phase), it was found
    that some records may be missed if thousands of updates occurred
    against the same row. The outcome of this may be an ALAA447E
    msg, ALAA440E msg, or even an abend or incorrect output. In
    other words, it is indeterminate as to how missing some records
    will exactly affect the process, and therefore this fix should
    be applied in such cases (i.e., many updates to same row)
    regardless of the exact outcome.
    
    OTHER KEYWORDS: ALAA447E ALAA440E ALAA447 ALAA440
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis Tool.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: During merge processing (aka, LOG       *
    *                      APPLY phase), it was found that some    *
    *                      records may be missed if thousands of   *
    *                      updates occurred against the same row.  *
    *                      The outcome of this may be an ALAA447E  *
    *                      msg, ALAA440E msg, or even an abend or  *
    *                      incorrect output. In other words, it    *
    *                      is indeterminate as to how missing      *
    *                      some records will exactly affect the    *
    *                      process, and therefore this fix should  *
    *                      be applied in such cases (i.e., many    *
    *                      updates to same row) regardless of the  *
    *                      exact outcome.                          *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK53299

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    230

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2007-09-20

  • Closed date

    2007-09-26

  • Last modified date

    2007-11-02

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

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

Modules/Macros

  •    ALABSDS
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R220 PSY UK29632

       UP07/10/09 P F710

  • R230 PSY UK29633

       UP07/10/09 P F710

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":"230"}]

Document Information

Modified date:
30 March 2021