IBM Support

PK54674: POINTER CHECKER ERRORS (BROKEN DATABASE) ON PITR OF 4 BASES AT A TIME.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When recovering 4 bases at a time results in recovered database
    being broken (pointer checker errors). Further investigation
    shows the mixing of IRLM=N and IRLM=Y logs causes the problem.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users that use DRF version 3 release     *
    *                 one might be affected.                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: When doing a PITR recovery using logs   *
    *                      created from a batch job, DRF ends with *
    *                      RC=0, but the Open Unit Of Recovery     *
    *                      Report shows open UORs even though the  *
    *                      PITR time is after the close of the     *
    *                      log. The result is that the recovered   *
    *                      database is incorrect, which is evident *
    *                      when running HPPC on the recovered      *
    *                      database.                               *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    FRXRBUF0 was missing code in some paths, though it did exist in
    others. This code stores with the open UOR the PRILOG End Time
    of the Batch Log that contains the UOR.  When the UOR manager
    encounters an 06 Batch End log record it must match the Batch
    Log's PRILOG End Time in the 06 with PRILOG End Time stored with
    all open UORs so that all UORs for that batch log can be applied
    to the database.  Otherwise, the UOR would be left open, the
    database would not be updated and the OPEN UOR Report would
    reflect this.
    

Problem conclusion

  • AIDS: RIDS/UTIL RIDS/DBS DBS/UTIL
      GEN:
    
    *** END IMS KEYWORDS ***
    FRXRBUF0 is modified to fix the problem.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK54674

  • Reported component name

    IMS DB RECOVERY

  • Reported component ID

    5655I4400

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2007-10-14

  • Closed date

    2007-12-20

  • Last modified date

    2008-04-30

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

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

    PK55850 UK32533

Modules/Macros

  • FRXRBUF0
    

Fix information

  • Fixed component name

    IMS DB RECOVERY

  • Fixed component ID

    5655I4400

Applicable component levels

  • R310 PSY UK32533

       UP07/12/22 P F712

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX88Z","label":"IMS Database Recovery Facility"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 April 2008