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

is necessary, your online dumps already reflect the batch updates. TMF would need to apply
only those database changes that occurred after online dumps were taken.
• When you create a new table and want to provide file recovery protection for it, make an
initial online dump of the table after creation.
• Certain DDL and statements and utility commands invalidate previous online dumps. For
instance, whenever you load tables, update metadata, create new indexes, partition tables
or indexes, or restructure or move the database, you should always make new online dumps
to ensure the new status of the database is recorded correctly. See “Operations That Impact
TMF Online Dumps” (page 52).
• TMF can retain online dumps of several generations of each file. The number of generations
retained depends on the RETAINDEPTH option of TMF configuration parameters. Each
generation of an online dump provides a starting point for a file recovery operation. You gain
greater reliability by keeping extra generations of online dumps, but the site needs additional
tape management for the online dumps and audit trails.
For more information, see the TMF Operations and Recovery Guide.
Operations That Impact TMF Online Dumps
Some SQL/MX operations impact TMF online dumps and require specific recovery actions. For
example, some operations invalidate TMF catalog entries, which invalidates TMF online dumps.
These SQL/MX operations delete or significantly alter the file labels or the file contents.
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.
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/MX 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 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,
the timestamps can cause inconsistencies that leave the table unusable.
For more information on making online dumps, see the TMF Operations and Recovery Guide.
Table 4 (page 52) summarizes SQL/MX operations that can invalidate online dumps.
Table 4 SQL/MX Operations That Impact TMF Online Dumps
Recovery StrategyEffectOptionOperation
Make online dumps of all partitions of
the new index to provide TMF file
recovery protection.
Does not invalidate any
existing online dumps.
POPULATE (or no
option specified)
CREATE INDEX
After the population has been
completed through a separate
Does not invalidate any
existing online dumps.
NO POPULATE
POPULATE INDEX command, make
new online dumps of the new index
to provide TMF file recovery
protection.
Make online dumps of the target
object after the DUP operation to
Does not invalidate any
existing online dumps.
DUP
52 Planning Database Security and Recovery