SQL/MX 3.1 Reference Manual (H06.23+, J06.12+)

SQL/MX Utilities
HP NonStop SQL/MX Release 3.1 Reference Manual—663850-001
5-128
Considerations for UPGRADE
If the REPORTONLY option is specified, only the initial error checking is performed
and no upgrading takes place. If the LOG TO option is also specified, the list of
affected schemas to be upgraded is written to the output file.
•
LOG TO
If the LOG TO option is specified, the command writes a log of its progress to either
the specified oss-file or to the home terminal. If the CLEAR option is used and if
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
Recovery of a Failed UPGRADE Utility
The RECOVER command is extended to allow recovery of a failed UPGRADE
command.
RESUME
enables you to continue the processing of the original command, starting at the
point of interruption.
************** Time: <time> Process: <process> Log opened **************
RECOVER ALL METADATA
[ RESUME | CANCEL ]
[ optional output spec ]
optional output spec is:
[ { [ LOG TO ] OUTFILE oss-file
[ CLEAR ] | LOG TO HOMETERM } ] [ REPORTONLY ]