TMF Reference Manual (G06.26+)

TMFCOM Commands
HP NonStop TMF Reference Manual—522418-003
3-243
RECOVER FILES
Because the MAP NAMES option restores files only to the same instance of TMF, you
cannot use this option to restore these files to another system.
When you use the MAP NAMES option, the files in the new locations have the same
user IDs and attributes as those in the old locations.
When you use the MAP NAMES option, the FROMARCHIVE option is also used in all
cases, even if you do not explicitly select it. For recovery to a new location, Enscribe
files are purged and restored before recovery is started. However, you should create
SQL objects before recovery is started to keep the catalog consistent.
Note. If you specify the MAP NAMES option, you cannot use the RECOVERVDPPHASE1
option.
Caution. The MAP NAMES option does not correct interdependencies between files. In
particular, the following restrictions apply:
•
MAP NAMES does not add SQL objects into a SQL catalog; instead, you must manually
add the new tables to the SQL catalog you wish before you perform the recovery.
•
MAP NAMES treats file partitions as distinct files; thus, recovered file partitions must be
manually updated to reflect any changes.
•
MAP NAMES does not update file labels for alternate key files.
•
TMF does not apply SQL file-label modification records encountered in an audit trail for an
object being recovered to a new location. Thus, the file label in an online dump must
match the file label of the newly created target, and the target’s file label must match the
final form of the source-file label to ensure a successful recovery.
For full guidelines and restrictions about the recovery of SQL objects, see the discussion
“Recovering Files to New Volumes, Subvolumes, or File IDs” in SQL/MP Installation and
Management Guide and the discussion “Recovering Files to New Locations” in SQL/MX
Installation and Management Guide.
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.