TMF Operations and Recovery Guide (G06.24+)

Managing SQL Objects
HP NonStop TMF Operations and Recovery Guide—522417-002
C-8
Impact of SQL Operations on Online Dumps
performing the drop commits or aborts. A dump could accidentally be deleted from the
TMF catalog if the last assigned object in the dump is changed to the released state.
For more information about dropping audited objects, see the SQL/MP Installation and
Management Guide or the SQL/MX Installation and Management Guide as appropriate
to your SQL software.
Impact of SQL Operations on Online Dumps
The impact of certain SQL operations on TMF online dumps is summarized in Table
C-1, which shows whether these operations invalidate online dumps. To execute any
of them, you must have either the super user ID or ownership of all affected tables.
To maintain TMF file recovery protection for any affected objects, you should make
new online dumps of the affected objects after doing any of the listed operations. Even
if the operation fails to complete properly, file labels or content might be affected.
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
TMFCOM 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.
Caution. If a full recovery of a table is needed and the catalog is not going to be recovered,
then the timestamps can cause inconsistencies that leave the table unusable. For more
information, see the discussion “Responding to Accidental Loss of an Audited SQL/MP Object”
in the SQL/MP Installation and Management Guide, or “Responding to Accidental Loss of an
Audited SQL/MX Object” in the SQL/MX Installation and Management Guide.
Table C-1. Impact of SQL Operations on TMF Online Dumps (page 1 of 3)
SQL
Statement Option Effect Recovery Strategy
ALTER INDEX
and
ALTER TABLE
(allowed in
SQL/MP only)
NO AUDIT Invalidates all online
dumps of the affected
object. The object
does not have any
TMF file recovery
protection if it is not
audited.
If the AUDIT attribute is later
turned back on, make new
online dumps of all partitions
of the index or table to retain
TMF file recovery protection.
ADD
PARTITION
(with no data
movement)
Does not invalidate
any existing online
dumps.
Make a new online dump of
the added partition to retain
TMF file recovery protection.
ADD
PARTITION
(with data
movement)
Invalidates all online
dumps of the source
partition.
Make new online dumps of
the source partition and
added partition to retain TMF
file recovery protection.