Recovering HALDB databases "prior" to an OLR

You can use IMS Database Recovery Facility for HALDB recoveries that are prior to any OLR recorded in DBRC (that is, before an OLR start time).

About this task

By specifying an RCVTIME that is equal to or less than the OLR start time recorded in DBRC, you can recover to a state prior to when the OLR began. After the recovery, the ACTIVE DBDS is set to whichever data sets were active at that recov-to-time and OLREORG CURSOR ACTIVE is set to NO.

If the RCVTIME exactly matches the OLR start time recorded in DBRC, it is not considered to be "into" an OLR. The data set is recovered to a time just prior to the OLR starting. The ACTIVE DBDS is set to whichever data set was active before the OLR started and OLREORG CURSOR ACTIVE is set to NO.

Notes:
  • You are not restricted to recovering back to the most recent OLR.
  • Any recovery of a HALDB partition which crosses an OLR boundary causes the Partition REORG# to be incremented in the RECON.

Procedure

  1. Specify an IMS Database Recovery Facility RCVTIME that is equal to or less than the OLR start time.
  2. Note: The databases must either be /DBRd prior to the recovery or specify DBRCMD(GLOBAL) and STACMD(GLOBAL) on the IMS Database Recovery Facility START command. The indexes/ILDSs must be rebuilt and all recoverable data sets must be image copied. It is recommended to specify HALDB(BOTH) and ICNDX(Y) as well as IB(BLD_PRIMARY,BLD_SECONDARY(ALL)) and IC(....) statements to perform these tasks under IMS Database Recovery Facility. The PC statement is recommended if you have the IMS pointer checker tool(s).
    Run IMS Database Recovery Facility.
  3. Verify that the ACTIVE DBDS flag was set to whichever data set was previously active for that time stamp.
  4. Verify that the OLREORG CURSOR ACTIVE flag was set to NO.
  5. Verify that the ICNEEDED COUNT is 0 and/or ICNEEDED was set to OFF for all database components (partition data sets, ILDSs, primary indexes if PHIDAM, and secondary indexes if applicable).
  6. Verify that the RECOVERY NEEDED COUNT is 0 and/or RECOV NEEDED flag was set to OFF for all database components.
  7. Verify that the databases are started and can be accessed online.