SQL/MP Installation and Management Guide
Performing Recovery Operations
HP NonStop SQL/MP Installation and Management Guide—523353-004
11-15
Operations That Invalidate TMF Online Dumps
For detailed steps to recover accidentally dropped tables, see Recovering Tables on 
page 11-19.
Operations That Invalidate TMF Online Dumps
Some SQL/MP operations invalidate TMF online dumps, affecting TMF file recovery. 
The TMF subsystem maintains the integrity and consistency of databases for online 
transaction processing. You must understand how SQL/MP and the TMF subsystem 
work together so that you do not lose or damage important data.
To execute any SQL/MP operation that invalidates online dumps, you must have either 
the super ID or ownership of all affected tables.
Some SQL/MP operations invalidate TMF catalog entries, which invalidates TMF 
online dumps. These SQL/MP operations delete or significantly alter the file labels or 
the file contents. 
To keep file recovery protection for these files, you must make new TMF online dumps 
after any of these operations. Even if the operation fails to complete properly, file labels 
or file contents might be affected. Plan to make new TMF online dumps even if one of 
these operations is unsuccessful.
If you need to recover an affected table or index to a point before the SQL operation 
that invalidated the applicable dump, the TMF file recovery process might require that 
you manually modify the online and audit dump entries in the TMF catalog by using the 
TMF ALTER DUMPS or ADD DUMPS command. To preserve consistency, this type of 
a recovery must include not only the tables or indexes directly affected, but also all 
partitions of each table or index and all logically related objects in the database. 
For more information on making online dumps, see the TMF Operations and Recovery 
Guide. 
Note. If you follow the first approach, and any dependant objects of the dropped table were 
registered in different catalog(s), those catalogs must also be recovered along with the catalog 
in which the dropped table was registered.
Caution. If the TMF catalog entries are incorrect and a problem occurs with the database, you 
could lose the ability to use TMF file recovery operations to recover the database.
Caution. If a full recovery of a table is needed and the catalog is not going to be recovered, 
the timestamps can cause inconsistencies that leave the table unusable.










