IBM Support

PM46442: POSSIBLE MISSING RECORDS AFTER FORCED ARCHIVE LOG.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Log records may be missed in the following condition: an active
    log is forceably archived (i.e., manually as opposed to DB2
    automatic archive, before it is full). Subsequently some DML
    is logged onto that active log, but very little other activity
    occurs within it, so that active log comprises mostly activity
    that existed prior to the previous forced archive. if LAT is
    then run against that activity resulting in either that 'new'
    active log being the first log to be read for a non-data sharing
    group, or the first log to be read for any member of a data
    sharing group, then those records may be missed.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis Tool.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Log records may be missed in the        *
    *                      following condition: an active log is   *
    *                      forceably archived (i.e., manually as   *
    *                      opposed to DB2 automatic archive,       *
    *                      before it is full). Subsequently some   *
    *                      DML is logged onto that active log,     *
    *                      but very little other activity occurs   *
    *                      within it, so that active log comprises *
    *                      mostly activity  that existed prior to  *
    *                      the previous forced archive. if LAT is  *
    *                      then run against that activity          *
    *                      resulting in either that 'new' active   *
    *                      log being the first log to be read for  *
    *                      a non-data sharing group, or the first  *
    *                      log to be read for any member of a      *
    *                      data sharing group, then those          *
    *                      records may be missed.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Apply the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM46442

  • 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-08-25

  • Closed date

    2011-11-30

  • Last modified date

    2012-01-01

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

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

    UK74367

Modules/Macros

  •    ALAAA8   ALAALOG  ALAFRA   ALAFR1D  ALAFR1I
    ALAFR1V  ALAFR6   ALAFR64  ALALB3
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R320 PSY UK74367

       UP11/12/09 P F112

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