SQL/MP Installation and Management Guide

Performing Recovery Operations
HP NonStop SQL/MP Installation and Management Guide—523353-004
11-8
Completing the Planning Phase
Completing the Planning Phase
You should prepare for restoring the database when the database is consistent and
inactive. To complete planning for restoring the database, perform these steps.
1. Ensure that the database is not active.
2. If you are not planning a volume-mode RESTORE operation, described under
Restoring a Database as a Planned Event on page 11-9, create an EDIT file
containing SQL statements that will re-create your catalogs. The statements must
specify the same security and the same owners for each catalog and for each
catalog table that can be individually secured.
The catalog security is the security of the catalog tables, except for the USAGES,
TRANSIDS, and PROGRAMS tables, which can be secured individually. In the
system catalog, the CATALOGS table can also be secured individually. To find out
the security and owner of your catalog tables, you can query the catalog TABLES
table as follows:
>> LOG log-file CLEAR;
>> SELECT TABLENAME, SECURITYVECTOR, GROUPID, USERID
+> FROM catalog-name.TABLES
+> WHERE TABLENAME = "\system.$volume.catalog-name.TABLES";
To find out the security and owner of the USAGES, TRANSIDS, and PROGRAMS
tables, you can specify those tables in a query:
>> SELECT TABLENAME, SECURITYVECTOR, GROUPID, USERID
+> FROM catalog-name.TABLES
+> WHERE TABLENAME = "\system.$volume.catalog-name.USAGES"
+> OR TABLENAME = "\system.$volume.catalog-name.TRANSIDS"
+> OR TABLENAME = "\system.$volume.catalog-name.PROGRAMS";
The EDIT file must contain these two types of statements:
•
A CREATE CATALOG statement for each catalog on the node. To make sure
the catalog is re-created with the same security, use the SECURE option to
specify the catalog security:
>> CREATE CATALOG $volume.subvolume SECURE "security-
string";
•
An ALTER TABLE statement for any table whose security or owner is different
from the catalog security or owner:
>> ALTER TABLE $volume.subvolume.PROGRAMS
+> SECURE "security-string"
+> OWNER "group-num, user-num" ;
3. Back up the entire node and use the AUDITED option so that both audited and
nonaudited files are dumped. To back up the node, enter:
BACKUP $TAPE, *.*.*, OPEN, AUDITED, LISTALL