Recovery Procedures

You can recover a database in the following situations:
view
You can recover a database in the following situations:
  • Recovery from media problems
  • Recovery from integrity problems
  • Restoring the entire database with SARDBASE RESTORE
  • Recovery using forward recovery data set data
    Notes:
    • For more information about complete descriptions of the utilities used in all of these recovery procedures, see Database Utilities.
    • If you use
      Deliver
      direct-to-
      View
      archival, you can temporarily reroute the reports to the JES spool using the
      Deliver
      ARCH
      nn
      parameters. When the
      View
      archival task is restarted, it archives those reports from JES.
Minimizing Non Archival Time
Certain database recovery processes can take a considerable amount of time, depending on the size of the database. You can minimize non archival time during database recovery by restoring the database in phases. After the first phase (master index restore), you can resume archival.
If a SARDBASE RESTORE is required for a database, you can:
  • Initially RESTORE only the master index (substantially less time than restoring all data)
  • Use the TLOAD control statement of the SARTDR to restore the number of generations you require for production
  • Resume operation of the
    View
    archival task, archiving to the newly-restored database
  • Use SARRSP to restore the rest of the corrupted database to the newly-restored database
    This can be done during archival.