IBM Support

PK52776: DATABASE CORRUPTION USING DRF 310 AFTER A PITR RECOVERY TERMINATING WITH A RC=0 ALSO LOOP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Database corruption using DRF 310 after a PITR recovery
    terminating with a RC=0 is the reported symptom. During recreate
    using the same data other symptoms occured i.e. loop/hang
    conditions, storage fragmentation, and sychronization problems
    when processing large quantities of data.
    Forward fit of 210 APAR PK52222
    Additional keywords ABENDU0385  U0385 0000000A
    ABENDU385
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of DRF version 3 release one might *
    *                 be affected.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Undetected data corruption results      *
    *                      when an image copy with bad data is     *
    *                      used as input to recovery or log data   *
    *                      is either corrupted or overlayed        *
    *                      during DRF processing.                  *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    Undetected data corruption can result if the image copy RBA
    being processed is smaller than the prior image copy RBA values.
    This can happen if the image copy has been corrupted but is
    still used as input to recovery.  This can also happen if
    processing in DRF overlays the internal contents of log records
    or log data has been corrupted.'
    

Problem conclusion

  • AIDS: RIDS/UTIL RIDS/DBS DBS/UTIL
      GEN:
    
    *** END IMS KEYWORDS ***
    FRXRBUF0 is modified to add the check to make sure that the log
    sequence number is in the correct range.
    FRXIVCN0 and FRXIOCN0 are modified to check the current RBA of
    Image Copy that is about to apply. If the current RBA is
    smaller than the prior image copy RBA values, abend with U385-A.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK52776

  • 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-09-12

  • 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:

    UK32534

Modules/Macros

  • FRXIOCN0 FRXIVCN0 FRXRBUF0
    

Fix information

  • Fixed component name

    IMS DB RECOVERY

  • Fixed component ID

    5655I4400

Applicable component levels

  • R310 PSY UK32534

       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