SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Planning Database Security and Recovery
HP NonStop SQL/MX Installation and Management Guide—523723-004
5-9
Recovering Dropped Database Objects
•
Whenever you request a TMF online dump, back up that dump to tape and use the
TMFCOM INFO DUMPS, OBEYFORM command to obtain a hard copy with that
tape. For good TMF practice, be sure to maintain a backup copy of the entire TMF
catalog on tape.
°
If you perform the dumps with separate groups of disks (for example, a dump
for each group attached to a particular processor), the dumps for your SQL/MX
objects and catalogs will be scattered among numerous tapes. The advantage
of this approach is that you are less likely to miss a vital object during the
recovery process. The disadvantage is that it requires a lot of work: you need
to continually keep track of all interdependent objects, and process many tapes
during recovery.
°
If you perform collective dumps of the SQL/MX catalog and all its objects, this
command might enable faster recovery, but you must continually update the
SQL OBEY (script) files that you use to rebuild SQL/MX objects.
Finally, before dropping any individual view or index, be sure to save a current OBEY
(script) command file to re-create the view or index. You can obtain this file by issuing
the necessary SHOWDDL commands.
Before dropping a table, run the SHOWDDL command or be sure that the
SAVE_DROPPED_TABLE_DDL attribute is ON to ensure that you can re-create the
table and its indexes as they were defined at the time of the drop.
Also, make sure that you have these items at hand:
•
Current online dumps of the objects.
•
Hard copies of the TMF catalog and the object dumps, obtained with the TMFCOM
INFO DUMPS, OBEYFORM command.
Note. You can use OBEY command files containing TMFCOM command scripts for
TMF tasks that you perform repeatedly.