SQL/MP Installation and Management Guide

Performing Recovery Operations
HP NonStop SQL/MP Installation and Management Guide—523353-004
11-2
Restoring Individual SQL Objects
Restoring Individual SQL Objects
The RESTORE utility can replace SQL objects that have been backed up on tape. For
this discussion, restoring SQL objects and databases means you are replacing existing
objects in the same location. For a discussion about using the RESTORE utility to
move SQL objects and databases, see Section 9, Moving a Database.
RESTORE automatically creates SQL catalogs for SQL objects being restored if a
catalog does not exist and the command includes the AUTOCREATECATALOG ON
option.
During object restoration, if RESTORE determines that a referenced catalog does not
exist, RESTORE directs the catalog manager to create the catalog, and alter the
catalog security and owner ID, to match the security and owner ID at the time of the
backup operation. After the catalog security and owner are altered, the user performing
the restore might not have the appropriate security to update the catalog;
consequently, the objects might not be restored in the catalog.
The default for RESTORE is AUTOCREATECATALOG OFF.
Restoring Catalogs
The RESTORE utility cannot directly recover a catalog. TMF recovery methods protect
SQL/MP catalogs. All of the catalog tables are audited so that they can be archived by
using the TMF subsystem and recovered by using either TMF volume recovery or file
recovery procedures.
Restoring Collations
If you restore objects and programs that use collations, you must restore the collations
first. For audited collations, however, use the TMF file recovery operation, discussed
under Restoring Objects With TMF Recovery Operations on page 11-11, instead of
RESTORE.
Restoring Tables
Typically, you would want to use the RESTORE utility to recover programs or
nonaudited tables. For audited tables, use the TMF file recovery operation discussed
under Restoring Objects With TMF Recovery Operations on page 11-11.
The RESTORE utility replaces the file with a file of the same type. You cannot use
RESTORE to drop an SQL table and restore it as an Enscribe file or use it to drop an
Enscribe file and restore it as an SQL table.
When restoring a table, the RESTORE utility tries to duplicate all partitions, indexes,
and protection views. In addition, the utility restores all comments and constraints to
the COMMENTS and CONSTRNT tables, respectively, of the target catalog.
RESTORE does not attempt to restore any dependent shorthand views unless their
names are explicitly included in the file set list that specifies which objects to restore.