SQL/MP Installation and Management Guide

Performing Recovery Operations
HP NonStop SQL/MP Installation and Management Guide—523353-004
11-3
Restoring Tables
These are options of the RESTORE utility and how they affect restoring SQL objects:
•
RESTORE allows the use of a qualified file-set list to identify the source objects to
be restored.
•
The PURGE option effectively performs an SQL DROP statement before restoring
the table. By using the default, PARTONLY OFF, with the PURGE option, you can
drop all partitions of a table and all the dependencies, which are indexes,
partitions, protection views, comments, and constraints; then, you can restore them
all.
•
The INDEXES IMPLICIT or INDEXES EXPLICIT option controls the restoration of
indexes. The default is for indexes to be implicitly restored with the underlying
table. If you specify INDEXES EXPLICIT, the indexes are not automatically
restored with the underlying table unless specified in the file set list.
•
Some of the inconsistencies or other problems that can occur by using RESTORE
with the INDEXES EXPLICIT option are:
°
All components might not be restored.
°
Pointers in the file labels could point to the wrong file. (This is more likely to
happen when you are moving objects with the MAP NAMES clause, however.)
°
Index data might be inconsistent with the underlying table data.
•
By specifying the PARTONLY ON option, you can restore a partition of a table
separately or restore multiple partitions collectively. Only partitions identified by the
file set list are purged and restored.
•
Some of the inconsistencies or other problems that can occur by using RESTORE
with the PARTONLY option are:
°
The security of partitions might be inconsistent.
°
Recovery might commence before RESTORE PARTONLY determines whether
recovery is truly viable.
°
Parallel RESTORE operations might cause deadlock.
°
Programs might be invalidated unnecessarily.
°
Physical attributes of partitions might be mismatched.
°
The definition of a recovered partition might be inconsistent with those of its
associated partitions if the object definition was changed because the backup
was performed.
Caution. You must be extremely careful when using the INDEXES EXPLICIT option because
it can cause tables to become inconsistent.
Caution. You must be extremely careful when using the PARTONLY ON option because it can
cause tables to become inconsistent.