SQL/MP Installation and Management Guide

Performing Recovery Operations
HP NonStop SQL/MP Installation and Management Guide—523353-004
11-10
Restoring a Database as an Unplanned Event
6. Verify the database by using the VERIFY utility; following is an example of the
VERIFY command:
>> VERIFY *.*.*;
7. Drop and re-create any invalid shorthand views. By using VERIFY in Step 6, you
can identify any invalid shorthand views.
8. Perform new TMF online dumps of all catalogs and audited SQL objects.
Restoring a Database as an Unplanned Event
If you were not able to plan for restoring the database because of a catastrophic
failure, you must begin to restore the system by using the most recent backups and
TMF online dumps.
To restore the database as an unplanned event:
1. Perform TMF file recovery for all audited files as described under Restoring
Objects With TMF Recovery Operations on page 11-11.
2. Issue the RESTORE command to recover Enscribe and nonaudited files. Use a set
of commands that match those used in the BACKUP process. Also include the
AUTOCREATECATALOG ON option in the RESTORE command to create the
necessary catalogs. An example of the RESTORE command, where *.*.*
represents unaudited and Enscribe files, follows:
RESTORE $TAPE, *.*.*, AUTOCREATECATALOG ON, OPEN, &
LISTALL, TAPEDATE
You should not use the SQLCOMPILE option in the RESTORE command with this
type of restoration. The program compilations could cause invalid programs
because dependent tables, views, and indexes might not yet be restored when the
program is restored.
To restore OSS files, use the appropriate OSS utility.
3. After you have restored all the tables and views that the programs use, SQL
compile the programs.
4. Manually resolve any inconsistencies in the data between audited and nonaudited
tables. At this step, your database might be consistently defined in the catalogs,
but the data in the audited and nonaudited files might be inconsistent. The
inconsistency occurs from the time difference between the backups and the online
dumps.
5. Verify the database by using the VERIFY utility; enter:
>> VERIFY *.*.*;
6. Drop and re-create any invalid shorthand views. Using VERIFY in Step 5 identifies
any invalid shorthand views.
7. Perform new TMF online dumps of all catalogs and audited SQL objects.