SQL/MX 2.x Reference Manual (H06.04+)

SQL/MX Utilities
HP NonStop SQL/MX Reference Manual—540440-003
5-81
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
•
You must have the privileges required to perform the utility you are recovering.
•
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.
•
object-name can exist on a remote node and be referenced by the current
RECOVER operation if the remote node is visible to the local node.
Examples of RECOVER
•
This example recovers and by default cancels the default the incomplete SQLDDL
operation on the specified table:
RECOVER TABLE mycat.myschema.mytable;
•
This example identifies the table affected by a failed utility operation and instructs
RECOVER to cancel the failed utility operation:
RECOVER TABLE mycat.myschema.mytable CANCEL;