IBM Support

PM23866: DUPLICATE LRSN CAUSING SORTING SEQUENCES FOR GENERATED DB2 LOADFILE FROM LOG ANALYSIS TOOL

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • DB2 can log duplicate LRSN for log records in certain situations
    and this can cause sorting sequence issues when sorting by the
    LRSN and other fields. The sorting sequence issue only occurs
    for rows where DB2 logs an update as an insert and a delete. Log
    Analysis Tool allows options to pack the LRSN so the LOADFILE
    can be sorted on this field. While packing the LRSN, Log
    Analysis Tool also packs the RBA of the log record. When the
    update was a delete and an insert, two different RBA values were
    used in the packing. This is not a problem unless this row has
    the same LRSN as another filtered row of activity. This APAR
    will use the lower of the two RBA values to ensure an easier and
    more reliable sorting sequence.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis Tool               *
    ****************************************************************
    * PROBLEM DESCRIPTION: DB2 can log duplicate LRSN for log      *
    *                      records in certain situations and this  *
    *                      can cause sorting sequence issues when  *
    *                      sorting by the LRSN and other fields.   *
    *                      The sorting sequence issue only occurs  *
    *                      for rows where DB2 logs an update as    *
    *                      an insert and a delete. Log Analysis    *
    *                      Tool allows options to pack the LRSN    *
    *                      so the LOADFILE can be sorted on this   *
    *                      field. While packing the LRSN, Log      *
    *                      Analysis Tool also packs the RBA of     *
    *                      the log record. When the update was a   *
    *                      delete and an insert, two different     *
    *                      RBA values were used in the packing.    *
    *                      This is not a problem unless this row   *
    *                      has the same LRSN as another            *
    *                      filtered row of activity. This APAR     *
    *                      will use the lower of the two RBA       *
    *                      values to ensure an easier and more     *
    *                      reliable sorting sequence.              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    APPLY the PTF
    

Problem conclusion

Temporary fix

Comments

  • APPLY the PTF
    

APAR Information

  • APAR number

    PM23866

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    310

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-10-04

  • Closed date

    2010-11-03

  • Last modified date

    2010-12-02

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

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

Modules/Macros

  •    ALAAC
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R310 PSY UK61897

       UP10/11/09 P F011

  • R320 PSY UK61898

       UP10/11/09 P F011

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

Document Information

Modified date:
17 March 2021