Using LOGONLY or LOGAPPLY ONLY with point-in-time recoveries

• PIT_RBA: the point to which the table space is recovered

• START_RBA: the point at which the point-in-time recovery was performed

If the log range used for a LOGONLY or LOGAPPLY ONLY recovery includes both the PIT_RBA and the START_RBA from a point-in-time recovery, the log range between those log points is ignored.

 The following figure shows how PIT_RBAs and registered log points are used during LOGONLY or LOGAPPLY ONLY recoveries

The FROMLOGPOINT of a LOGONLY recovery is obtained from the log point that is stored in the header page, while LOGAPPLY ONLY obtains it from the syntax.

When the FROMLOGPOINT of a LOGONLY or LOGAPPLY ONLY recovery is greater than the PIT_RBA of a point-in-time recovery and the TORBA of the LOGONLY or LOGAPPLY ONLY recovery is greater than or equal to the START_RBA of the point-in-time recovery (see the following figure), BMC AMI Recover does not allow a recovery to be performed. If BMC AMI Recover attempted this recovery, the restored copy may include some, but not all, updates that are located between the PIT_RBA and the START_RBA. Recovery of the log records found after the START_RBA depends on none of those updates being present. If you must perform such a recovery and you are using a non Db2 backup, you must select a backup before the PIT_RBA.

 The following figure shows when a recovery is not allowed by BMC AMI Recover

JOB 1:

RECOVER TABLESPACE X.Y INDEP OUTSPACE
    MODEL &VCAT.DSNDBC.&DB.&SP.I001.&DSNUM 
    TOCOPY LASTCOPY

JOB 2:

RECOVER TABLESPACE X.Y FROMLOGPOINT LASTCOPY 
        LOGAPPLY ONLY