G06.31 Software Installation and Upgrade Guide

Preparing to Fall Back
G06.31 Software Installation and Upgrade Guide—544626-002
14-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.1.1 on page 2-12. For
NonStop SQL/MX Release 2.0, to minimize the risks involved in 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 G02 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 or to a pre-T6031D46^ABK
product version unless you do not have any Safeguard aliases created in
DSM/SCM. You must run the macro before you start DSM/SCM.
Before falling back, you do not need to delete the Safeguard aliases. When you
run the FALLBACK macro, the aliases are removed from DSM/SCM when the
database tables that contain the aliases are deleted. The Safeguard aliases still
exist on the system; however, they cannot be used by DSM/SCM. You must enter
the deleted Safeguard aliases in DSM/SCM when you install successfully the new
RVU.
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 the previous RVU
7. Loading the system from the previous operating system image
8. Starting the applications
Note. At this point, if you did not copy or export the DSM/SCM FALLBACK macro and the
DSM/SCM PVU is pre-T6031D46^ABK, see Notes on the FALLBACK Macro on page 1-23
before beginning the DSM/SCM backout of the RVU.