SQL/MP Installation and Management Guide

Performing Recovery Operations
HP NonStop SQL/MP Installation and Management Guide—523353-004
11-32
PUP RENAME
3. Check that dependent objects residing on other volumes have also been recovered
and re-create objects as necessary.
For example, a table resides on another volume, but a dependent index resides on
the newly labeled disk volume. If the index was not recovered, re-create the index.
You should also check that all view definitions are current and that all shorthand
views were recovered. Re-create any views that were not recovered.
4. Depending on the date and time of the most recent BACKUP and TMF recovery
point, the restore operations might not be able to retrieve a consistent database
with mixed audited and nonaudited files. Manually resolve any inconsistencies
between audited and nonaudited database files.
5. SQL compile any programs that were invalidated by this process and that reside
on other volumes. Also, SQL compile all programs restored to $VOL to validate
them and register them in a catalog.
6. Verify the database by using the VERIFY utility; an example of the VERIFY
command follows:
>> VERIFY $VOL.*.*;
7. Drop and re-create any shorthand views that might have been left in an invalid
state. Any invalid shorthand views will be identified in Step 6.
8. Make new TMF online dumps of all catalogs and audited objects on the volume.
PUP RENAME
If a volume is renamed inadvertently, use the PUP RENAME command to rename the
volume to its previous name.
If a volume must be renamed, only a knowledgeable database administrator should
attempt the operation. Files must be backed up to tape and then restored to the
renamed volume. This task is similar to that described in Steps for Moving a Database
on page 9-25. Note that volumes can be recovered only if all the objects on the
renamed volume are described in catalogs on the same volume. If this is the case, use
the Guardian BACKUP and RESTORE utilities to back up the volume, as follows:
1. Determine all the SQL objects to be renamed and all dependencies. Produce hard-
copy reports containing this information.
Caution. Do not use RESTORE to restore an index; doing so might cause inconsistencies in
the database.
Caution. The use of PUP RENAME is extremely dangerous because it can corrupt a
database. The PUP RENAME operation renames the files on a volume, but SQL catalogs and
file labels still contain the old name. Do not use PUP RENAME on disks that contain SQL
catalogs or objects. PUP RENAME should only be used for volumes that do not contain SQL
catalogs or other SQL objects.