IBM Support

PM03796: LOG APPLY PHASE OF OBJECT RECOVERY TAKES TOO LONG BECAUSE RECOVER UTILITY IS READING BACK TOO FAR IN THE LOG.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2 Recovery Expert for z/OS LOG APPLY phase of object recovery
    takes too long because recover utility is reading back too far
    in the log.
    A possible error that can occur during the LOG APPLY phase is
    the following:
    
    DSNU547I !E81B DSNUCAIN - LOGONLY RECOVER CANNOT PROCEED BECAUSE
             THE STARTING RBA=X'000000000000' IN THE HEADER PAGE
             PGNO=X'00000000' FOR
             TABLESPACE RETRDB.RETRTS5 IS INVALID.
    
    This PTF will resolve this issue as well as bring changes to
    REBUILD INDEX generation to speed rebuild index performance.
    
    ISPF portion of RE will generate index rebuilds cards for all
    the indexes in each TS in one set of rebuild index cards.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Recovery Expert.                *
    ****************************************************************
    * PROBLEM DESCRIPTION: DB2 Recovery Expert for z/OS LOG APPLY  *
    *                      phase of object recovery takes too      *
    *                      long because recover utility is         *
    *                      reading back too far in the log.        *
    *                      A possible error that can occur during  *
    *                      the LOG APPLY phase is the following:   *
    *                      DSNU547I !E81B DSNUCAIN - LOGONLY       *
    *                       RECOVER CANNOT PROCEED BECAUSE         *
    *                       THE STARTING RBA=X'000000000000' IN    *
    *                       THE HEADER PAGE PGNO=X'00000000' FOR   *
    *                       TABLESPACE RETRDB.RETRTS5 IS INVALID.  *
    *                      This PTF will resolve this issue as     *
    *                      well as bring changes to REBUILD INDEX  *
    *                      generation to speed rebuild index       *
    *                      performance. ISPF portion of RE will    *
    *                      generate index rebuilds cards for all   *
    *                      the indexes in each TS in one set of    *
    *                      rebuild index cards.                    *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM03796

  • Reported component name

    DB2 REC EXPERT

  • Reported component ID

    5697H7400

  • Reported release

    220

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-12-16

  • Closed date

    2010-01-18

  • Last modified date

    2010-02-01

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

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

    UK53636

Modules/Macros

  • ARY$BULJ ARY#OBEX ARY@DOOD ARY@MSGS ARY@OCPY
    ARY@OREN ARY@ORSE ARY@SCPY ARY@SNPD ARY@SOFF ARY@SOFR ARY@SUCB
    ARY@YCRD ARY@ZTGT ARYLEVEL ARYRBLDC H30R220J
    

Fix information

  • Fixed component name

    DB2 REC EXPERT

  • Fixed component ID

    5697H7400

Applicable component levels

  • R220 PSY UK53636

       UP10/01/23 P F001

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.

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVQTW","label":"Db2 Recovery Expert"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.2.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 February 2010