G06.25 Software Installation and Upgrade Guide

Preparing to Fall Back
G06.25 Software Installation and Upgrade Guide—529430-001
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, G06.24, and
G06.25) on page 1-31. 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 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 your previous RVU
7. Loading the system from the previous operating system image
8. Starting the applications
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