Installation and Upgrade Guide

Overview of Installing G06.24
G06.24 Software Installation and Upgrade Guide—528593-005
1-29
NonStop SQL/MX Release 2.0 (G06.23 and G06.24)
SQL/MX Release 2.0 delivers the newly architected, standards-based SQL/MX tables
for NonStop servers. SQL/MX Release 2.0 provides general availability support for
operations against SQL/MP tables. Support for SQL/MX tables is not included in the
G06.24 RVU. The function, when available, will be shipped as SPRs and is planned to
be compatible with G06.23 and G06.24.
Migration Considerations for SQL/MX Release 2.0
Metadata tables created and used by SQL/MX Release 2.0 running on the G06.23 and
G06.24 RVUs are different from those metadata tables used on prior SQL/MX
releases, and the tables are very different from those used by SQL/MP. You must be
on at least Release 1.8 to migrate to SQL/MX Release 2.0, and Release 1.8 is the only
version of SQL/MX, which you can fall back to from Release 2.0.
Only the metadata from R1.8 should be migrated to the Release 2.0 format. To
facilitate migrating metadata, a migrate utility is provided with Release 2.0.
Migration and fallback considerations do apply. See also TMF (G06.23 and G06.24) on
page 1-38 and DP2 (G06.16, G06.23, G06.24). In multinode installations, where
queries must access data on other nodes, all nodes must migrate to SQL/MX Release
2.0 at the same time. A mixture of nodes running SQL/MX Release 1.8 and SQL/MX
Release 2.0 is not supported. Because SQL/MX Release 2.0 is an optional product, it
can be un-installed after it has been installed on an 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 SQL/MX.
A quick summary of fallback and migration considerations include:
•
To fall back to SQL/MX Release 1.8, you must reinstall your previous RVU and
certain versions of some pre- or co-requisite software product.
•
Fallback to SQL/MX releases earlier than SQL/MX Release 1.8 is not supported. If
you are using a SQL/MX release that preceded Release 1.8, you must migrate to
an RVU that supports Release 1.8 (G06.18 through G06.22) before migrating to
SQL/MX Release 2.0 (G06.23 or later).
•
If you are migrating from an SQL/MP or SQL/MX Release 1.8 environment, do not
delete your SQL/MP metadata tables until you are sure you do not need to fall
back. (Deleting these tables will prevent a successful fallback.)
•
SQL/MX Release 2.0 applications you have developed prior to fallback are not
usable with the SQL/MX Release 1.8.
•
To fall back to an SQL/MP database environment, you do not have to reinstall your
previous RVU. (SQL/MP is included in the G06.23 and G06.24 RVUs.) To fall back
to an Enscribe database environment, you do not have to reinstall your previous
RVU. (Enscribe is included in the G06.23 and G06.24 RVUs.)
•
Applications that you compiled with the SQL/MX Release 2.0 compiler need to be
recompiled with the previous release of the SQL compiler after fallback.