SQL/MP Installation and Management Guide

Performing Recovery Operations
HP NonStop SQL/MP Installation and Management Guide—523353-004
11-24
Recovery Example
The resulting display is identical to the one shown under Recovery Example on
page 11-20. The objects exist once again. However, the EMPLOYEE table does
not yet contain any data.
6. When the objects were purged, TMF set the INVALID and RELEASED attributes of
the online dumps for the objects to ON. Before you can recover the objects, you
must first reset these attributes to OFF, using the TMFCOM ALTER DUMPS
command:
~ ALTER DUMPS ( &
~ $DATA.PERSNL.EMPLOYEE &
~ ,$DATA.PERSNL.EMPLIST &
~ ,$DATA.PERSNL.MGRLIST &
~ ,$DATA.PERSNL.XEMPNAME &
~ ,$DATA.PERSNL.XEMPDEPT &
~ ,$DATA.SALES.ORDREP &
~ ) &
~ ,INVALID OFF &
~ ,RELEASED OFF &
~ ,SERIAL 73
Now, you are ready to recover the table and its dependent objects.
7. Proceed with recovery by entering the TMFCOM RECOVER FILES command:
~ RECOVER FILES ( &
~ $DATA.PERSNL.EMPLOYEE &
~ ,$DATA.PERSNL.EMPLIST &
~ ,$DATA.PERSNL.MGRLIST &
~ ,$DATA.PERSNL.XEMPNAME &
~ ,$DATA.PERSNL.XEMPDEPT &
~ ,$DATA.SALES.ORDREP &
~ ) &
~ ,FROMARCHIVE &
~ ,TOFIRSTPURGE
The objects are now recovered in the database, but additional work might remain
to be done because of possible inconsistencies between the objects’ file labels on
disk and the corresponding information for them in the SQL catalog.
TMF does not update or insert entries in the SQL catalog during a RECOVER
FILES operation for a table. As it performs recovery, TMF attempts to automatically
synchronize the objects’ create time and redefinition time between the catalog and
the file label on disk. If TMF cannot perform this synchronization, it displays EMS
Message 203 (with Subsystem Error 9038) for each inconsistency. For example:
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. Normally, the objects to be recovered are spread across different disk volumes and
subvolumes. However, in this example, some of the objects are located in the same subvolume
as the SQL/MP catalog. In such a case, use care to avoid recovering the catalog tables so that
the current state of the catalog is maintained.