SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)

Falling Back to SQL/MX Release 1.8
HP NonStop SQL/MX Database and Application Migration Guide540435-005
8-2
Obtaining SQL/MX Release 1.8
prerequisite or corequisite software products. See Obtaining Corequisite Independent
Products on page 8-2.
Fallback to SQL/MX releases earlier than SQL/MX Release 1.8 is not supported.
Obtaining SQL/MX Release 1.8
Obtain the latest version of SQL/MX Release 1.8 that is supported by the previous
RVU of the system. For more information, see NonStop SQL/MX Releases
on
page 2-2 and RVUs and Supported SQL/MX Releases
on page 2-7.
Be aware that installing an SQL/MX release on your system overwrites the previous
SQL/MX release. Although NonStop SQL/MP and NonStop SQL/MX can reside on the
same node, multiple releases of NonStop SQL/MX cannot reside on the same node.
Only one release of SQL/MX software can reside on a node at a time. For example, if
SQL/MX Release 1.8 is installed on a node, SQL/MX Release 2.0 or SQL/MX Release
2.1 cannot be installed at the same time.
Obtaining Corequisite Independent Products
Obtain any corequisite independent products for the version of SQL/MX Release 1.8
that you will re-install on your system. Some corequisite independent products include:
RDF
NonStop Server for Java
JDBC Driver for SQL/MX
For more information, see the
H06.nn or G06.nn Release Version Update
Compendium.
Assessing Changes to the Applications and Database in
SQL/MX Release 2.x
If you migrate from SQL/MX Release 1.8 to SQL/MX Release 2.x, you can use the
fallback procedure in Steps for Falling Back From SQL/MX Release 2.x to SQL/MX
Release 1.8 on page 8-3. Falling back to an SQL/MX release earlier than SQL/MX
Release 1.8 is not supported.
The complexity associated with falling back to SQL/MX Release 1.8 varies depending
on the types of changes performed under SQL/MX Release 2.x:
You did not make any changes.
If the only work you performed in SQL/MX Release 2.x was to migrate the
metadata and then run existing SQL/MX Release 1.8 applications, falling back to
Release 1.8 is straightforward. Before you reinstall a previous RVU, use the DROP
SQL command to uninstall the SQL/MX Release 1.8 metadata that you migrated to
SQL/MX Release 2.x. After you reinstall the SQL/MX Release 1.8 RVU, no other
changes are required.