IBM Support

PK21218: RSR SHADOW DB WAS CORRUPTED BY RECEIVING GAP DURING OFR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The RSR shadow DB was corrupted by receiving gap during OFR.
    The UP2 in L2 gap was not applied by OFR.
    --------------------------------------------------------
              (L1)    (L2)
    A-ACT |---------|  GAP  |
               UP1     UP2      (L3)    (L4)
    B-ACT                     |-------|----------->
                                 UP3     UP4
    TRK   |-/DBR----------------------------/STA-->
    --------------------------------------------------------
    L1-L4 are log data sets.  UP1-UP4 are update log records.
     1. /STA (OFR)
         => L1 and L3 were allocated
     2. Received L2 GAP
         => L2 and L4 were allocated
     3. DFS4056I DB STARTED
           => UP2 lost !!!
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All IMS V8 Remote Site Recovery ( RSR )      *
    *                 users may be affected.                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: RSR shadow DB corrupted by OFR when     *
    *                      there is a tail gap in one of the       *
    *                      required logs.                          *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    The RSR shadow DB was corrupted by receiving gap during OFR.
    The UP2 in L2 gap was not applied by OFR.
    --------------------------------------------------------
              (L1)    (L2)
    A-ACT |---------|  GAP  |
               UP1     UP2      (L3)    (L4)
    B-ACT                     |-------|----------->
                                 UP3     UP4
    TRK   |-/DBR----------------------------/STA-->
    --------------------------------------------------------
    L1-L4 are log data sets.  UP1-UP4 are update log records.
     1. /STA (OFR)
         => L1 and L3 were allocated
     2. Received L2 GAP
         => L2 and L4 were allocated
     3. DFS4056I DB STARTED
         => UP2 lost
    

Problem conclusion

  •  AIDS: RIDS/DBRC RIDS/UTL DBRC UTL
      DEP: NONE
      GEN:
    
    *** END IMS KEYWORDS ***
    DSPOFRLR has been changed to detect a tail gap in the set of
    logs required for OFR of any given database.  If there are DB
    changes (a later ALLOC) after the gap the DB will be stopped
    with,
         MSGDFS4108A START FOR DATABASE dbname FAILED:
                     04 MISSING LOG
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK21218

  • Reported component name

    IMS V8

  • Reported component ID

    5655C5600

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-03-09

  • Closed date

    2006-04-06

  • Last modified date

    2006-10-04

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

    PK20241

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

    UK13340

Modules/Macros

  •    DSPOFRLR
    

Fix information

  • Fixed component name

    IMS V8

  • Fixed component ID

    5655C5600

Applicable component levels

  • R800 PSY UK13340

       UP06/04/14 P F604

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVRBJ","label":"System Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 October 2006