TMF Operations and Recovery Guide (G06.26+)

Recovery Methods
HP NonStop TMF Operations and Recovery Guide—522417-003
7-23
Responding to Incorrect Updates to the Database
•
Do not delete or move audit-trail files that are in the ZTMFAT subvolume. Audit-
trail files have a file code of 134, which you can view by using the TACL FILEINFO
command.
Responding to Incorrect Updates to the Database
Use the RECOVER FILES command to correct certain problems that have caused
database inconsistencies, such as:
•
An audited file has been mistakenly purged (see next subsection).
•
An audited file has been purged of data by the PURGEDATA command (use the
TIME option).
•
A database needs to be recovered to a specific time (use the TIME option).
•
An application program has updated the database in an inconsistent manner (use
the TIME option).
Responding to Accidental Loss of an Audited File
You can recover an audited file that has been accidentally deleted as follows:
1. Use the INFO DUMPS, DETAIL command to see if the TMF catalog still has an
entry for the most recent online dump for the file:
•
If there is no entry for the file, issue an ADD DUMPS command to replace the
entry. Use the output from a previous INFO DUMPS command or consult your
hardcopy dump tracking forms to obtain the necessary information.
•
If there is an entry for the file but the dump status is released or invalid, issue
an ALTER DUMPS command with the INVALID OFF and RELEASED OFF
options to change the dump status.
2. Issue another INFO DUMPS, DETAIL command to make sure the TMF catalog has
a correct entry for an online dump for the file.
3. Issue a RECOVER FILES command with the FROMARCHIVE option and either
the TIME option or the TOFIRSTPURGE option and any other options needed to
recover the purged file. If you want to recover all files up to the first file purged in a
fileset, it is more straightforward and risk-free to use the TOFIRSTPURGE option
rather than the TIME option.
4. Make a new online dump of the file once the file recovery process has completed.
Responding to Accidental Loss of an Audited SQL Object
If an SQL object has been accidentally dropped from the system, you may be able to
recover the object by using TMF file recovery together with SQL conversational
interface commands. The particular recovery steps depend on whether the object
dropped was a view, an index, or a table. Performing the recovery, especially in the
case of a table, requires substantial knowledge of both SQL and TMF. For details