HP BACKCOPY Reference Manual page 167

For more information about restoring SQL objects, including guidelines for restoring and moving
individual objects and entire databases, and renaming objects, see the SQL/MP Installation and
Management Guide.
When you use PARTONLY OFF and INDEXES IMPLICIT:
◦
When a base table is restored to disk, any SQL protection views defined on the table
are restored automatically. Any SQL shorthand views that depend on the table are not
restored unless they are explicitly named in the restore-files.
◦
When a base table is restored, any constraints associated with the table are restored
automatically.
◦
When a base table, index, or SQL shorthand view is restored, any comments associated
with these objects are restored automatically.
NOTE: SQL tables can be restored only if the program file from RESTORE is licensed. If you
use DSM/SCM to install RESTORE, licensing is automatic. If you do not use DSM/SCM, to
license the RESTORE program file use the FUP LICENSE command.
◦
An SQL protection view is automatically restored when its base table is named in
restore-files. An SQL protection view cannot be restored independent of the base
table on which the protection view is dependent.
BACKUP and RESTORE do not work with remote SQL tables if SQL is not installed on the local
node.
All SQL programs, as well as all programs that use tables, indexes, or views, that you restore
must be recompiled. To automatically recompile all SQL programs when they are restored,
use the SQLCOMPILE ON option in your RESTORE command.
CAUTION: It is critical that the CATALOGS and MAP NAMES mapping lists are complete even
when recovering an individual partition:
If the CATALOGS option is specified, every associated catalog must be mapped.
If the MAP NAMES option is specified, every partition must be mapped.
If the maps are incomplete or incorrect, severe catalog inconsistencies for the object will result.
These inconsistencies are quite difficult to repair, so make sure to avoid them.
To restore an SQL object to a different location, use the MAP NAMES option. If the location
is on a different system, you must specify both the old and new system names. For example:
MAP NAMES (\oldsys.subvol.filename to
\newsys.subvol.filename)
RESTORE cannot directly recover a catalog. TMF recovery methods protect SQL catalogs.
Catalog tables are audited so that they can be archived with TMF and recovered with either
TMF autorollback or rollforward.
If the SQL catalog (where SQL objects are registered) does not exist, use the
AUTOCREATECATALOG ON option in your RESTORE command. An SQL catalog is created,
and RESTORE inserts appropriate entries with the first instance of an SQL object.
To register SQL objects in a different SQL catalog during a restore than they were originally
registered in, use the CATALOGS option. If the different catalog is on a different system, use
a fileset that describes the destination fileset, not the original.
SQL catalogs backed up with the SQLCATALOGS ON option can be restored as normal SQL
tables with a file code of 0.
RESTORE purges the existing object on disk before it begins writing files from the backup
tape. If an error occurs during the RESTORE process and the INDEXES IMPLICIT option was
RESTORE Guidelines and Examples 167