Fast Recover job not using the SYSIBM.SYSLGRNX table
search cancel

Fast Recover job not using the SYSIBM.SYSLGRNX table

book

Article ID: 279900

calendar_today

Updated On:

Products

Fast Recover for DB2 for z/OS

Issue/Introduction

Run a recovery of a tablespace starting from a Full Image Copy. 

RECOVER TABLESPACE ...  
FULLDD IMAGCOPY                         
SORT-LOG                             
STARTLOGPOINT X'nnnnnnnnnnnnnnnnnnnn'
ENDLOGPOINT   X'mmmmmmmmmmmmmmmmmmmm'
OBIDXLAT old-obid, new-obid                       
NO-NEW-COPY                            


The Fast Recover Job seems to read the whole Db2 Log data sets, disregard of the intervals in the SYSIBM.SYSLGRNX table. 

Resolution

Fast Recover when performing OBIDXLAT does not read from the SYSIBM.SYSLGRNX table. The Fast Recover Job will read directly the BSDS data sets to determine the Db2 Log data sets that will be read based on the STARTLOGPOINT and ENDLOGPOINT parameters.  
 
Fast Recover is designed this way to work even when the source Db2 subsystem is not reachable, then working on this way, a Fast Recover Job will be able to recover from another Db2 subsystem even if that Db2 subsystem is not online.