G06.24 Software Installation and Upgrade Guide

G06.24 Software Installation and Upgrade Guide—528593-005
17-1
17
Loading the Previous RVU and
Resuming Normal Operations
This section describes how to load the previous RVU back into the memory of each
processor in the server and resume normal operations.
Alerts
Before performing a system load, note:
•
If you are returning to an RVU prior to the G06.06 RVU, check that you have
replaced the bootstrap program on the primary system disk named $SYSTEM to
the earlier version by following the instructions in Section 6, Replacing the Disk
Bootstrap Microcode (Pre-G06.06) (specifying the previous SYSnn).
•
Do not close the System Startup dialog box while startup is in progress. If you
attempt to close the dialog box, a TSM message dialog box appears, indicating
that the system startup process will be stopped if you continue.
•
If you stop a system startup before it has finished, the state of your system
becomes unpredictable. You might need to perform another system startup to
enable the system to resume normal operation.
•
If you must stop the system startup process, click Abort (the process should take
effect within 30 seconds).
•
If you fall back and then try to migrate again to a G06.18 or later RVU, DSM/SCM
might notify you during the Apply that the CLEANOSS macro must be run. The
current OSS environment is being managed by a logical target other than the one
trying to manage OSS files with the current DSM/SCM Build/Apply. You must
cancel the Apply, and then run the CLEANOSS macro. See DSM/SCM
(T6031D46) Fallback on page 1-27.
•
Before falling back, to minimize the risks involved with falling back without a clean
TMF shutdown, use the appropriate SQL (MX or special MP) utility to delete all
native-format SQL/MX objects and their resource forks. This step must be done
before entering the first START TMF after you have performed a system load with
the previous RVU. See NonStop SQL/MX Release 2.0 (G06.23 and G06.24) on
page 1-28 before continuing.