PM80707: RESTORE SYSTEM FROMDUMP DOES NOT FALLBACK TO SLB RESIDING ON TAPE IN CASE THE FALLBACK TO THE MOST RECENT SLB FAILS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• RESTORE SYSTEM FROMDUMP might fail with
  DSNU1637I   327 18:09:43.66 DSNUVBRD - RESTORE SYSTEM UTILITY
  FAILED BECAUSE NO FLASHCOPY IS AVAILABLE
  DSNU1631I   327 18:09:43.66 DSNUVBRD - RESTORE SYSTEM UTILITY
  FAILED BECAUSE THE CALL TO DFSMSHSM FAILED WITH
  RC =  X'00000000' REASON = X'00000000'.
  This can happen if FROMDUMP is specified and if restore of most
  recent SLB fails for certain reasons, it goes to second one
  found, and attempts fallback. If it's on disk, it will fail, and
  it does not look for an SLB on tape, and does not fall back any
  further.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 10 for z/OS users of RESTORE SYSTEM  *
  *                 utility with FROMDUMP specified.             *
  ****************************************************************
  * PROBLEM DESCRIPTION: RESTORE SYSTEM FROMDUMP may attempt     *
  *                      to restore a system level backup        *
  *                      which has not been dumped to tape,      *
  *                      or may fall back and attempt to         *
  *                      do so after a prior failure.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
    This APAR improves the way RESTORE SYSTEM with FROMDUMP
  chooses the system level backup (SLB) it will attempt to
  restore, or fall back to, in order to address several
  problems.
  
    1. If FROMDUMP is specified, RESTORE SYSTEM may choose an
  SLB to restore which has not been dumped to tape, causing the
  RESTORE to fail or to fall back to an earlier SLB.
  
    2. If FROMDUMP is specified and the restore of the most
  recent SLB fails, it may fall back and attempt to restore a
  previous SLB.  If that SLB is only on disk, the RESTORE will
  fail, and will not attempt to fall back further.
  
    3. If RESTORE SYSTEM fails to restore an SLB, but falls
  back to an earlier SLB and restores it successfully, the
  RESTORE SYSTEM utility ends with RC8 and DB2 will function as
  though the system has not been properly recovered.
  
    Messages related to these issues include the following:
  
  MSGDSNU1631I - RESTORE SYSTEM UTILITY FAILED BECAUSE THE
                 CALL TO DFSMSHSM FAILED.  SEE THE HSM
                 ACTIVITY LOG FOR HSM MESSAGES INDICATING THE
                 CAUSE OF THE ERROR.
  
  MSGDSNU1616I - THE CALL TO DFSMSHSM TO RECOVER SYSTEM
                 FAILED.  PLEASE SEE MESSAGE ARC1806E IN THE
                 HSM ACTIVTY LOG.  A RETRY MAY BE ATTEMPTED
                 IF AN APPROPRIATE BACKUP VERSION CAN BE
                 IDENTIFIED.
  
  MSGDSNU1619I - RESTORE SYSTEM UTILITY FAILED, BECAUSE
                 THERE ARE NO BACKUP SYSTEM HISTORY ENTRIES
                 IN THE BSDS WITH A DATA COMPLETION
                 LRSN/RBA PRIOR TO THE LOG TRUNCATION POINT
  
  MSGDSNU1637I - RESTORE SYSTEM UTILITY FAILED BECAUSE NO
                 FLASHCOPY IS AVAILABLE
  
  MSGDSNR050I  - DB2 STARTED IN SYSTEM RECOVER PENDING MODE
  
  MSGDSNY014I  - DB2 WAS STARTED WITH ACCESS(MAINT)
  
  additional keywords:  DSNU1631I DSNU1616I DSNU1619I DSNU1637I
                        DSNR050I DSNY014I DSNU1618I
  

Problem conclusion

• RESTORE SYSTEM utility code was changed so that when FROMDUMP
  is specified (or requested via ZPARM setting
  RESTORE_RECOVER_FROMDUMP = YES), only system level backups that
  have been dumped to tape will be used to restore.  If the most
  recent SLB on tape prior to the requested log truncation point
  fails, the next most recent SLB on tape will be used.
    A change to the DB2 documentation is made, similar to the
  following:
    DB2 messages
  MSGDSNU1618I - RESTORE SYSTEM UTILITY FAILED BECAUSE THERE ARE
                 NO BACKUP SYSTEM HISTORY ENTRIES IN THE BSDS
  and
  MSGDSNU1619I - RESTORE SYSTEM UTILITY FAILED, BECAUSE THERE ARE
                 NO BACKUP SYSTEM HISTORY ENTRIES IN THE BSDS
                 WITH A DATA COMPLETION LRSN/RBA PRIOR TO THE LOG
                 TRUNCATION POINT
  
  will both have the following text added to their existing
  respective Explanations:
  
  If you ran RESTORE SYSTEM with the FROMDUMP option, references
  in this message to BACKUP SYSTEM history entries refer only to
  history entries for backups that were dumped to tape.
  

Temporary fix

Comments

• ž**** PE14/07/12 FIX IN ERROR. SEE APAR PI11924  FOR DESCRIPTION
  

APAR Information

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

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

  UK95633 PM93233

Modules/Macros

• DSNUVARS DSNUVBRD
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK95633

     UP13/07/23 P F307

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.