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

Performing Recovery Operations
HP NonStop SQL/MX Installation and Management Guide—544536-007
12-6
Recovering Metadata
You can recover SQL/MX objects to a different location even when the source objects
have not been purged. You can create the target objects to match the source, and then
perform the recovery to obtain a copy of your source objects. Transactions can be
active against the source objects at the time of the recovery.
Recovering Metadata
TMF is the primary means of recovering metadata associated with catalogs, but other
methods exist.
You can use the TMF file recovery method to recover metadata associated with
catalogs to a point where they were consistent. If any tables of the catalog have the
undo-needed or redo-needed flag set, you should recover all the tables in the definition
schema for that catalog by following the TMF recovery procedures for this method. See
Recovering Files
on page 12-2 and Recovering Files With the TIME Option on
page 12-3.
If you have backup tapes available, you might be able to re-create catalogs by
restoring its tables using the BRCOM RESTORE command. See Restoring Catalogs
on page 12-23.
Caution. Use the TOFIRSTPURGE, TIME, or TOMATPOSITION option in the RECOVER
FILES command to avoid replaying the purge operation on a target object. If you do not do this
and the file-recovery process encounters a purge record for an object being recovered to a
different location, the process will terminate recovery of that object with these EMS messages:
NonStop TMF on \PLUTO *0437* RECOVER FILES [60]
FileRecovery Process #1: Encountered a purge record
for audited file $DATA17.ZSDT5356.J24Z5J00 while performing
FLABMOD REDO operation; Audit Trail Index #2, SNO #1,
RBA #22707360.
NonStop TMF on \PLUTO *0358* RECOVER FILES [60]
FileRecovery Process #1: Recovery on $DATA17.ZSDT5356.J24Z5J00
has terminated.
Caution. If you use the MAP NAMES option of the RECOVER FILES command to recover
files to a new location, you must immediately make new online dumps of the target data files
recovered. Without these new dumps, you will not have file-recovery protection for those files,
and subsequent file recovery operations can fail. In particular, if you later try to use old online
dumps of the target files to recover the target files to a point beyond the time that the last
RECOVER FILES command was issued, the file recovery process fails during the redo phase
and transmits EMS message 175:
Encountered a File Hiatus record for audit file filename at
audit trail Index #index, SNO #sno, RBA #rba.
Caution. Do not recover individual tables in a catalog. To keep an SQL/MX catalog consistent,
you must recover all the tables in the catalog as a set.