SQL/MP Installation and Management Guide

Performing Recovery Operations
HP NonStop SQL/MP Installation and Management Guide—523353-004
11-31
Recovering From Peripheral Utility Program (PUP)
Commands (D-series only)
•
You cannot specify the CLEANUP command within a user-defined TMF
transaction. The CLEANUP utility protects the database, however, by automatically
starting its own TMF transaction for each SQL object catalog description and file
label operated upon. If the CLEANUP utility fails during execution, only the deletion
of the last SQL object or partition is backed out.
Recovering From Peripheral Utility Program
(PUP) Commands (D-series only)
SQL/MP introduces new relationships between volumes and nodes in a network. Disk
names and node names are hard-coded references in the SQL/MP file labels and
catalogs. Incorrect use of PUP commands or of the MAP NAMES option in RESTORE
commands can lead to serious and possibly irreparable inconsistencies in an SQL/MP
database.
If your site needs to use any of these PUP commands on a volume with SQL objects,
you should carefully plan for a recovery method before using these commands:
LABEL, RENAME, COPY, FORMAT, REMOVE, REVIVE, DOWN and UP. Each listed
PUP command is discussed next.
PUP LABEL
PUP LABEL can irretrievably corrupt an SQL database. PUP LABEL should not be
used on disks containing SQL catalogs or objects with a few exceptions.
PUP LABEL can be used on volumes that do not contain SQL catalogs or SQL objects.
Do not attempt to recover a single volume when the database is distributed.
Use PUP LABEL on volumes with SQL objects in these situations:
•
To label a disk that has been destroyed and has completely corrupt data
•
To label all the disks on a node and recover the database with a complete restore
•
To PUP LABEL a disk following repair or replacement if a volume with SQL objects
has a catastrophic failure and no mirrored volume is available. In this situation, you
should label the disk with its previous name.
If you use the PUP LABEL command, these are the steps for recovering the volume:
1. Use RESTORE to retrieve the nonaudited database residing on this volume; an
example of the RESTORE command follows:
50> RESTORE $TAPE, $VOL.*.*, AUTOCREATECATALOG ON,
TAPEDATE, OPEN, LISTALL
2. Retrieve audited tables by using the most recent TMF online dumps and TMF file
recovery. To initiate a file recovery of all files on $VOL, enter this command through
one of the TMF interfaces; this example uses TMFCOM:
~ RECOVER FILES $VOL.*.*, CRASHOPEN OFF