Installation and Upgrade Guide

Preparing to Fall Back
G06.24 Software Installation and Upgrade Guide—528593-005
13-2
Summary of Fallback Tasks
•
Starting with the G06.23 RVU, there are fallback considerations regarding NonStop
SQL/MX Release 2.0. See NonStop SQL/MX Release 2.0 (G06.23 and G06.24) on
page 1-28. For SQL/MX Release 2.0: Before falling back, to minimize the risks
involved with falling back without a clean TMF shutdown, use the appropriate SQL
(MX or special MP) GOAWAY utility to delete all native-format SQL/MX objects and
their resource forks. Do this before entering the first START TMF after you have
performed a system load with the previous RVU.
•
If you installed the DSM/SCM D46 client version, you do not need to deinstall it.
However, you need to run the FALLBACK macro to convert both the Host and
Target database for use by the pre-T6031D46 version. You must run the macro
before you start DSM/SCM.
Summary of Fallback Tasks
1. Backing out the revision (DSM/SCM)
2. Replacing the bootstrap program on the primary system disk
3. Returning firmware to the previous versions (if needed)
4. Running ZPHIRNM
5. Halting the system processors
6. Removing any hardware not supported by your previous RVU
7. Loading the system from the previous operating system image
8. Starting the applications
Fallback Considerations for Specific Products
You might need to perform additional tasks for these products:
•
DP2
•
DLL (Dynamic-Link Libraries)
•
DSM/SCM
•
Spooler
•
Open System Services (OSS)
•
OSM and TSM
•
SMF
•
SQL/MX 2.0
•
TMF
•
WAN Manager (T8365)
Note. The FALLBACK macro can be retrieved from a D6031D46 distributed subvolume on
any G06.18 or later SUT. If the SUT is in the DSM/SCM archive, the FALLBACK macro can be
exported from the DSM/SCM archive.