PI51917: DB2 RECOVERY UTILITY WHICH RESTARTED FROM LOG APPLY PHASES SKIPPED THE APPLYING OF THE REST OF LOGS AND COMPLETED WITH RC0.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 RECOVERY utility which restarted from LOG APPLY phases
  skipped the applying of the rest of logs and completed with
  RC0.
  
  For example:
  DSNU021I  308 17:40:25.06 DSNUGASU - RECOVER UTILITY WITH
  UTILID = RECOV#CAT ENDED IN PHASE = LOGAPPLY, WILL ATTEMPT TO
  RESTART(CURRENT)
  DSNU050I  308 17:40:25.06 DSNUGUTC -  RECOVER TABLESPACE
  DSNDB01.SPT01
  DSNU1511I 308 17:40:25.10 DSNUCALA - FAST LOG APPLY WAS NOT
  USED FOR RECOVERY
  DSNU1510I   308 17:40:25.10 DSNUCBLA - LOG APPLY PHASE COMPLETE,
  ELAPSED TIME = 00:00:00
  DSNU500I    308 17:40:25.11 DSNUCBDR - RECOVERY COMPLETE,
  ELAPSED TIME=00:00:00
  DSNU010I    308 17:40:25.12 DSNUGBAC - UTILITY EXECUTION
  COMPLETE, HIGHEST RETURN CODE=0
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 11 for z/OS users of RECOVER with    *
  *                 RESTART.                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Loss of data after a RESTART of a       *
  *                      RECOVER TABLESPACE utility which        *
  *                      originally failed in the LOGAPPLY       *
  *                      phase.                                  *
  ****************************************************************
  * RECOMMENDATION: Apply corrective PTF when available          *
  ****************************************************************
  A RECOVER TABLESPACE utility failed in the LOGAPPLY phase.  A
  RESTART(CURRENT) was executed and completed RC0.  However, a
  subsequent CHECK INDEX showed many DSNU709I - NO INDEX ENTRY
  FOR ROW and DSNU711I - NO ROW FOR INDEX ENTRY messages.  In
  addition, the RESTART of the RECOVER in the LOGAPPLY phase
  showed no DSNU513I - RECOVER UTILITY LOG APPLY RANGE IS...
  messages in the job output, indicating the utility did not
  continue with LOGAPPLY.
  
  During RESTART, RECOVER did not scan through SYSLGRNX records
  to determine if there were any ranges of logs to apply.  This
  is always needed during RESTART, either CURRENT or PHASE.
  
  Additional Keywords:  MSGDSNU709I MSGDSNU711I MSGDSNU513I
  

Problem conclusion

• RECOVER utility code has been modified to correct the
  aforementioned problem.
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  UI32966

Modules/Macros

• DSNUCAIN
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RB10 PSY UI32966

     UP15/12/01 P F511

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.