Backup and Restore 2 Manual
BRCOM RESTORE Command
Backup and Restore 2 Manual—522696-019
7-65
SQL/MX Restore Examples
If the schema cat1.sch1 already exists with the subvolume name as that of the
BACKUP-OBJECTS, the schema will be restored with the subvolume name and
physical file names of the partitions as that of the BACKUP-OBJECTS.
While restoring to the remote node, if the schema cat1.sch1 already exists with the
subvolume name different from the BACKUP-OBJECTS, then while restoring table
or index partitions under the schema, the subvolume name of the existing schema
will be used and the file names will be as that of the BACKUP-OBJECTS.
Restoring All SQL/MX Catalogs
To restore all objects in all the catalogs:
BR> RESTORE =mytape, MX CATALOG *;
All the catalogs and their subordinate objects as shown in Table 7-7 on page 7-61 are
restored.
Restoring an SQL/MX Catalog
To restore all objects in the catalog, cat1:
BR> RESTORE =mytape, MX CATALOG cat1;
Catalog cat1 and all its subordinate objects as shown in Table 7-8 on page 7-65 are
restored:
Note. The KEEPGFN job option is supported only on systems running H06.11 or later H-series
RVUs.
Table 7-8. Catalog and Subordinate Objects Restored (page 1 of 2)
Catalog Schema Table
Table
Partition
or Index
Index
Partition Description
cat1 Catalog
-sch1 Subordinate schema of cat1
-tab1 Subordinate table of sch1
-tpart1 Subordinate table partition of
tab1 (last modified on 31 JUL
2002)
-ind1 Subordinate index of tab1
-ipart1 Subordinate index partition of
the index for tab1
-sch2 Subordinate schema of cat1
-tab2 Subordinate table of sch2
-tpart1 Subordinate table partition of
tab2