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-413
Considerations for UPGRADE
oss-file is an existing disk file, oss-file is cleared before logging begins.
Otherwise, the output is appended to the existing contents of oss-file. The
following is the format of the first line of log output:
The format enables you to recognize a log file easily. A command is rejected if it
specifies an existing non-empty oss-file that is not a log file.
Log file messages correspond to the EMS event messages. Regardless of the LOG TO
option, the UPGRADE utility will generate EMS events to the $0 primary collector that
documents the progress of the command. For information about error messages, see
the SQL/MX Messages Manual.
Error Conditions
The following are examples of the error conditions that might occur while executing the
UPGRADE utility:
•
An affected schema has a schema version that is higher than the target version.
•
No schemas are affected by the operation.
•
The RESTRICT option is specified or no option is specified, and one or more
related catalogs exist.
•
All of the following conditions are met:
°
The system catalog participates in the operation
°
Version 1200 schemas which do not participate in the operation exist on the
system
•
Concurrent UPGRADE operations are not supported.
Recovery of a Failed UPGRADE Utility
The RECOVER command is extended to allow recovery of a failed UPGRADE
command. Starting with SQL/MX 3.2, the UPGRADE utility also allows recovery of an
UPGRADE of metadata in an individual catalog.
************** Time: <time> Process: <process> Log opened **************
RECOVER ALL METADATA
[ RESUME | CANCEL ]
[ output-spec ]
RECOVER ALL METADATA IN CATALOG catalog
[ RESUME | CANCEL ]
[ output-spec ]