SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

creating the target object, the restore operation fails with Error 9037 as shown in this example,
and the object is not recovered:
NonStop TMF on \PLUTO *0202* RECOVER FILES [58]
OnLineRestore Process #1 OnlineDumpMgmt: *ERROR*
TMF-9037: $DATA17.ZSDT5356.J24Z5J00: File System error 11
occurred attempting to retrieve the SQL file label from disk.
If, for any other reason, the target object is inaccessible during the restore process, this process
also fails with Error 9037. For example:
NonStop TMF on \PLUTO *0202* RECOVER FILES [58]
OnLineRestore Process #1 OnlineDumpMgmt: *ERROR*
TMF-9037: $DATA17.ZSDT5356.J24Z5J00: File System error 1059
occurred attempting to retrieve the SQL file label from disk.
If TMF detects a mismatch between the source file’s label and the target file’s label, the object’s
recovery fails with Error 9036. For example:
NonStop TMF on \PLUTO *0202* RECOVER FILES [59]
OnLineRestore Process #1 OnlineDumpMgmt: *ERROR*
TMF-9036: $DATA17.ZSDT5356.J24Z5J00: The SQL label for this
file does not match the label for the source $DATA16.ZSDT5356.J24Z5J00.
If no mismatches occur, file recovery completes successfully. At the end of this recovery, perform
Step 9 through Step 15 under “Example: Recovering an Accidentally Dropped Table” (page 244)
for the target SQL/MX objects as needed.
When recovering dropped SQL/MX objects to a different location, you do not need to re-create
the source objects before the recovery. Only the target objects must exist and match the source
objects in terms of indexes, number of partitions, and so forth. You must alter the dumps of the
purged objects to reset the INVALID and RELEASED flags before attempting the recovery.
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.
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
238 Performing Recovery Operations