SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Performing Recovery Operations
HP NonStop SQL/MX Installation and Management Guide—523723-004
12-18
Recovering Tables
Because the objects now exist, you can also enter the ANSI name of the table
directly into the command:
$DATA01 SUBVOL 16>$system.zmxtools.mxgnames
HRDATA.PERSNL.EMPLOYEE -tmf
TMF 16>ALTER DUMPS ($DATA10.ZDST5356.JN9V5J00, &
>>> $DATA10.ZDST5356.JN9V5J01, &
>>> $DATA10.ZDST5356.NG59FJ00, &
>>> $DATA10.ZDST5356.NG59FJ01, &
>>> $DATA10.ZDST5356.NPFH8J00, &
>>> $DATA10.ZDST5356.NPFH8J01), INVALID OFF,&
>>> RELEASED OFF, SERIAL 70
8. Recover the table and its indexes.
To conduct the recovery, you use the TMFCOM RECOVER FILES command. You
can use the MXGNAMES output as input to the RECOVER FILES command, as
was done in Step 3:
$SYSTEM ZMXTOOLS 29> MXGNAMES HRDATA.PERSNL.EMPLOYEE -TMF
Hewlett-Packard NonStop (TM) SQL/MX Guardian Name Listing Utility
(c) Copyright 2003 Hewlett-Packard Development Company, LP.
(-- Table HRDATA.PERSNL.EMPLOYEE -- &
$DATA10,ZSDT5356.NG59FJ*,&
-- Index XEMPNAME ON HRDATA.PERSNL.EMPLOYEE -- &
$DATA10.ZSDT5356.JN9V5J*,&
-- Index XEMPDEPT ON HRDATA.PERSNL.EMPLOYEE -- &
$DATA10.ZSDT5356.NPFH8J* &
--End of Table HRDATA.PERSNL.EMPLOYEE -- &
)
TMF 3>RECOVER FILES (-- Table HRDATA.PERSNL.EMPLOYEE -- &
$DATA10.ZSDT5356.NG59FJ*,&
-- Index XEMPNAME ON HRDATA.PERSNL.EMPLOYEE--&
$DATA10.ZSDT5356.JN9VFJ*,&
-- Index XEMPDEPT ON HRDATA.PERSNL.EMPLOYEE--&
$DATA10.ZSDT5356.NPFH8J* &
--End of Table HRDATA.PERSNL.EMPLOYEE--&
),FROMARCHIVE, TOFIRSTPURGE
9. The objects are now recovered in the database. However, additional work might
need to be done because of possible inconsistencies between the objects’ file
labels on disk and the corresponding information for them in the SQL/MX
metadata.
Note. The ALTER DUMPS command does not allow partial wildcarding of the input file
names. Therefore, you will need to fully expand the file names from the MXGNAMES
output before using them in the ALTER DUMPS command.
Note. If, for any reason, the dumps were completely removed from the TMF catalog,
you would need to add them again, using the TMFCOM ADD DUMPS command. In this
command, you would also set the INVALID and RELEASED attributes to OFF.
Caution. Objects to be recovered are spread across different disk volumes and subvolumes.
However, if some of the objects are located in the same subvolume as the SQL/MX catalog or
schema, be careful to avoid recovering the catalog or schema tables, so that the current state
of the catalog is maintained.