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-414
Example of UPGRADE
catalog
specifies the ANSI name of the catalog that was specified in the original
UPGRADE command.
RESUME
enables you to continue with the processing of the original command, starting at
the point of interruption.
CANCEL
enables you to revert the changes made by the original command, thereby
returning the database to its original state. The default value is CANCEL.
output-spec
is the same as for the UPGRADE operation.
The RECOVER command must use the same mode of operation as the original
UPGRADE command:
•
If the original UPGRADE used the ALL METADATA mode of operation, then the
RECOVER must also use the ALL METADATA mode of operation.
•
If the original UPGRADE used the ALL METADATA IN CATALOG catalog mode of
operation, then the RECOVER must also use the ALL METADATA IN CATALOG
catalog mode of operation, and must specify the same catalog name.
In a distributed environment, the RECOVER command must be issued from the same
system where the original UPGRADE command was executed.
Error Conditions
The following are examples of the error conditions that might occur while executing the
RECOVER command:
•
An involved node has an incompatible version (because the version of the node
was modified between the time of the original operation and the time of recovery)
•
No corresponding UPGRADE or DOWNGRADE operation is recorded
•
The original command is still active
Example of UPGRADE
This example transforms all the metadata to the /usr/dbadmin/upgradeLog file:
UPGRADE ALL METADATA LOG TO OUTFILE /usr/dbadmin/upgradeLog
CLEAR;
Note. The RECOVER command does not need CASCADE option as it automatically recovers
the metadata for those catalogs that were affected by the original UPGRADE command.