TMF Operations and Recovery Guide (G06.24+)

Managing SQL Objects
HP NonStop TMF Operations and Recovery Guide—522417-002
C-7
Operations for Both SQL/MP and SQL/MX
If you use the TMF file-recovery feature, make an online dump of all Guardian files
associated with a newly created table: the file-recovery process cannot recover these
items unless at least one online dump of them has been made. (In SQL/MX, to return
a list of these items and their underlying Guardian file names, you can use the
MXGNAMES utility, described in the SQL/MX Reference Manual.) Any dependent
objects (such as indexes and views) are not automatically dumped with the table; you
must dump these dependent objects separately if you want them to be recoverable.
Duplicating an SQL Object
To duplicate one audited object to another audited object, enter the DUP command
from the SQL conversational interface. If you use the TMF file-recovery feature, you
should make an online dump of the new object.
You cannot duplicate an audited table within a user-defined TMF transaction; if you
attempt to do so, you will receive an SQL error.
Purging or Dropping an SQL Object
To purge audited tables, views, or indexes, use the PURGE command (available only
in SQL/MP) or the DROP statement from the SQL conversational interface. To purge a
schema (available only in SQL/MX) or a catalog, use the DROP statement from this
interface.
You can purge an SQL object only when TMF is active, the disk volume that contains
the object is enabled for TMF transaction processing, and the disk volume that
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, 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 it, the shorthand view is invalidated.
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
Caution. The audited SQL catalog contains definitions for all associated objects. TMF does
not integrate the definitions in this catalog with the recovered objects themselves. Be sure to
recreate the catalog definitions before performing a recovery; (normally, this is only an issue
when recovering a dropped object). 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.