IBM Support

PM53826: DUPLICATE LRSNS CAN CAUSE VARIOUS LOG ANALYSIS TOOL PROBLEMS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a duplicate LRSN is encountered in DB2 log records that
    modify the same  table row, the product cannot currently handle
    that as internal keys used to identify such activity will no
    longer be unique.  It is not possible to pinpoint every
    possible outcome of this situation, but noted results have
    included VSAM PUT errors and ALAA447 messages.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis Tool.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: If a duplicate LRSN is encountered in   *
    *                      DB2 log records that modify the same    *
    *                      table row, the product cannot currently *
    *                      handle that as internal keys used to    *
    *                      identify such activity will no longer   *
    *                      be unique.  It is not possible to       *
    *                      pinpoint every possible outcome of this *
    *                      situation, but noted results have       *
    *                      included VSAM PUT errors and ALAA447    *
    *                      messages.                               *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM53826

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-12-07

  • Closed date

    2012-01-11

  • Last modified date

    2012-02-02

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

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

Modules/Macros

  •    ALALFP
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R320 PSY UK75351

       UP12/01/21 P F201

  • R330 PSY UK75352

       UP12/01/21 P F201

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

Document Information

Modified date:
18 March 2021