SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

Table 4 SQL/MX Operations That Impact TMF Online Dumps (continued)
Recovery StrategyEffectOptionOperation
ensure TMF file recovery protection.
(This includes dumps of the table’s
partitions, plus dumps of partitions
associated with dependent indexes.)
Make online dumps of the target
object after the fastcopy operation to
Invalidates online dumps for
the target tables and target
indexes.
Fastcopy
ensure TMF file recovery protection.
(This includes dumps of the table’s
partitions, and dumps of partitions
associated with dependent indexes.)
Make a new online dump for all the
affected files to provide TMF file
recovery protection.
Turns on the audit bit for the
named file. Does not invalidate
any online dumps.
-a=onFIXUP utility
Online dumps are not needed until the
file’s audit bit is turned on.
Turns off the audit bit for the
named file, invalidates all
online dumps of the partition.
-a=off
Make new online dumps for all
partitions of the affected table.
Turns off the audit bit for an
empty table that does not have
IMPORT utility
any dependent indexes,
invalidates online dumps of all
partitions of this table.
Make an online dump of the new
partition to retain TMF file recovery
protection.
Does not invalidate online
dumps of existing partitions.
ADD (split range
partition)
(add hash partition)
MODIFY utility
(MODIFY INDEX and
MODIFY TABLE)
Make a new online dump of the
moved partition to retain TMF file
recovery protection.
Creates a new partition and
deletes the existing partition,
invalidating online dumps.
MOVE (simple move)
No action needed.Does not invalidate any online
dumps of the reused partition.
REUSE
Redo the online dumps of the restored
object to ensure TMF file recovery
protection.
Does not invalidate any
existing online dumps.
RESTORE
Using the TMF DUMP FILES Command
The TMF DUMP FILES command takes a series of Guardian file sets as its arguments. A file set is
an individual file name or a wild card representing multiple files. You can specify entire SQL/MX
schemas, using wild cards of the form DUMP FILES $*.subvolume.* to specify every Guardian
file in the SQL/MX schema whose schema subvolume is subvolume. You can then use an exclude
file list to specify individual files in the given schema that are not to be dumped. This process can
be repeated for each schema and subvolume combination.
For more information about using the MXGNAMES utility with TMF to facilitate use of the TMF
DUMP FILES command, see “Using Guardian Names with TMF, RDF, and Measure” (page 309).
In situations where large numbers of individual file names are to be included or excluded, note
that:
• The file set information for a given TMF DUMP FILES command cannot exceed 28 KB in length.
If the number of Guardian names to be specified exceeds this limit, specify them in multiple
commands.
• When specifying individual file names, it is also necessary to specify resource fork names.
TMF does not automatically include or exclude resource forks in an operation. They must be
included or excluded as part of the specified Guardian file set.
Using TMF for Transaction Recovery, Database Consistency, and Database Recovery 53