TMF Operations and Recovery Guide (G06.26+)
Managing SQL Objects
HP NonStop TMF Operations and Recovery Guide—522417-003
C-8
Impact of SQL Operations on Online Dumps
contains the SQL catalog in which the object is registered is enabled for TMF
transaction processing.
You cannot purge a SQL/MP nonaudited object within a user-defined transaction.
When a table is dropped in SQL/MP, all dependent views and indexes are also
dropped. If a dependent SQL/MP shorthand view cannot be dropped because the
requester of the purge operation does not have purge access to that SQL/MP
shorthand view, the shorthand view is invalidated.
When a table is dropped in SQL/MX, the dependent indexes are also dropped;
however, the dependent views are dropped only if CASCADE is specified in the DROP
request.
In SQL/MP, when the primary partition of a partitioned object is purged, all secondary
partitions of the object are also purged. In SQL/MX, all partitions of a table are purged
when the table’s ANSI name is dropped, and dependent objects are dropped if
CASCADE is specified in the DROP request.
When you drop an audited object, all online dump entries for the object are marked
RELEASED ON and INVALID ON in the TMF catalog whether the transaction
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
Certain SQL operations on objects in TMF online dumps invalidate these dumps, while
others do not. To execute any of these operations, you must have either the super
user ID or ownership of all affected tables. To determine which operations invalidate
online dumps and which do not, see the following discussions:
•
“Operations That Invalidate TMF Online Dumps” in the SQL/MP Installation and
Management Guide.
•
“Operations That Impact TMF Online Dumps” in the SQL/MX Installation and
Management Guide.
To maintain TMF file-recovery protection for any affected objects, you should make
new online dumps of the affected objects after doing any operation that might impact
an online dump. 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