SQL/MP Installation and Management Guide

Performing Recovery Operations
HP NonStop SQL/MP Installation and Management Guide—523353-004
11-29
Recovering Catalogs
can recover the table only by following all the steps under Recovery Example on
page 11-20.
•
You cannot use this method to recover a SQL object, along with its catalog, to a
new location.
Recovering Catalogs
There are several ways you can recover a catalog that becomes corrupt.
Because the catalog tables are TMF audited tables, you can use the TMF file recovery
method to recover the catalogs to a point where the catalogs were consistent. If any
tables of the catalog have the undo-needed or redo-needed flag set, you should
recover all the catalog tables by following the TMF recovery procedures for this
method, described under File Recovery and File Recovery With the TIME Option on
page 11-14.
If TMF recovery fails or is not available, you might be able to correct the
inconsistencies by using a licensed SQLCI2 process to change catalog entries.
Inconsistencies can arise from the incorrect use of PUP commands (D-series only) and
SCF commands (G-series only) or the incorrect use of licensed programs.
Purging Damaged Objects With the CLEANUP
Utility
The SQL/MP data dictionary, consisting of file labels and the catalog descriptions of
the files, is extremely reliable because the TMF subsystem is used to audit the catalog
tables and file labels. The catalog descriptions or file labels can become corrupt,
however, through misuse of the BACKUP and RESTORE utilities, the TMF RECOVER
FILES command, low-level system utilities such as PUP and TANDUMP, or because of
software or hardware problems.
When the catalog description or file label for an object becomes corrupt, it might not be
possible to purge the object by using the normal SQLCI PURGE or DROP command.
Caution. Do not recover individual catalog tables.To keep an SQL catalog consistent, you
must recover all the tables in the catalog as a set.
Note. A verify must be done on the restored table to find cases where USAGES entries are
not updated for dependent objects that are registered in a catalog table different from the main
table. If such cases are found, rows have to be added to the USAGES table of the other
catalogs using a licensed SQLCI2.