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

SQL/MX Statements
HP NonStop SQL/MX Release 3.2.1 Reference Manual—691117-005
2-311
Considerations for RECOVER
CANCEL
If you specify CANCEL, RECOVER attempts to undo the effects of the failed
utility operation. Otherwise, recovery fails. The default is CANCEL.
RESUME
If you specify RESUME, RECOVER attempts to carry the failed utility operation
to its completion. Otherwise, the recovery fails.
Considerations for RECOVER
•
object must be the same object that you were attempting to update with the
command that failed. Suppose that you have a table, cat.sch.t that has an index
cat.sch.i. You performed a POPULATE INDEX command for that index but it failed.
Consider these RECOVER operations:
>>recover table cat.sch.t;
*** ERROR[20209] Nothing remains to be recovered on
CAT.SCH.T.
--- SQL operation failed with errors.
>>recover index cat.sch.i;
--- SQL operation complete.
>>
•
At the completion of a RECOVER operation, the original failed operation should
either be completed as specified (RESUME) or completely rolled back (CANCEL).
•
Different utilities can be canceled or resumed depending on their failure status.
•
See the description of the individual utility operation to determine when and if
CANCEL or RESUME should be specified.
Examples of RECOVER
•
This example recovers and by default cancels the incomplete SQL DDL operation
on the specified table:
RECOVER TABLE mycat.myschema.mytable;
•
This example explicitly instructs RECOVER to cancel the failed utility operation:
RECOVER TABLE mycat.myschema.mytable CANCEL;
RECOVER SCHEMA Operation
Considerations for RECOVER SCHEMA
Examples of RECOVER SCHEMA