G06.28 Software Installation and Upgrade Guide

Overview of Installing G06.28
G06.28 Software Installation and Upgrade Guide—541688-001
1-35
NonStop SQL/MX Release 2.1.1
Migration Considerations for NonStop SQL/MX Release 2.1.1
Migration Notes for NonStop SQL/MX Release 2.1.1
Metadata tables created and used by NonStop SQL/MX Release 2.0 and later releases
are different from those metadata tables used on prior NonStop SQL/MX releases, and
the tables are very different from those used by NonStop SQL/MP. You must be on at
least Release 1.8 to migrate to NonStop SQL/MX Release 2.1.1. Releases 2.1, 2.0,
and 1.8 are the only releases of NonStop SQL/MX that you can fall back to from
Release 2.1.1.
If you are on NonStop SQL/MX Release 1.8, see also TMF on page 1-44 and DP2 on
page 1-29. In multinode installations, where queries must access data on other nodes,
all nodes must migrate to NonStop SQL/MX Release 2.0 or later at the same time. A
mixture of nodes running NonStop SQL/MX Release 1.8 and NonStop SQL/MX
Release 2.0 or later is not supported. Similar to other NonStop SQL/MX releases,
because NonStop SQL/MX Release 2.1.1 is an optional product, it can be uninstalled
after it has been installed on an NonStop S-series system. You must perform a system
load, but you do not need to change your current RVU unless you want to use a
previous release of NonStop SQL/MX.
•
To fall back to an SQL/MP database environment, you do not have to reinstall your
previous RVU. Before migrating to NonStop SQL/MX Release 2.1.1 from Release
1.8, HP recommends that you install one of these DP2 fallback SPRs or a
superseding SPR on the Release 1.8 system and test it sufficiently for production
use:
°
T9053APO, if the system uses the ODR feature
°
T9053APG, if the node does not use the ODR feature
Then you can migrate to G06.28. If a fallback becomes necessary at a later time,
you can fall back to the tested environment. For the steps to fall back from
NonStop SQL/MX Release 2.1.1, see the SQL/MX Installation and Management
Guide.
•
After falling back, if you have to remove any residual SQL/MX objects:
1. Use the FUP INFO command to locate any SQL/MX files remaining on the
system. Because SQL/MX objects reside in subvolumes that begin with the
letters ZSD, use this command to find them:
1>FUP INFO $*.ZSD*.*
2. Use the DELETE command of the DIRCHECK disk utility to delete the files.
For example:
2>$system.zutil.dircheck delete name $data08.zsdm819j.wdxhp600
Note. Note that a system load is required to install the DP2 fallback SPR. You must
perform the system load on your current RVU if you are migrating from Release 1.8. The
DP2 fallback SPR is already installed if you are on Release 2.0.