SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Falling Back From NonStop SQL/MX Release 2.1 or
Release 2.0
HP NonStop SQL/MX Installation and Management Guide—523723-004
A-3
Falling Back From Release 2.1 to Release 2.0
reinstalling Release 1.8. For information about these commands, see the SQL/MX
Reference Manual.
Falling Back From Release 2.1 to Release 2.0
If you migrate from Release 2.0 to Release 2.1, you might find it necessary to fall back
to Release 2.0.
To fall back from Release 2.1 to Release 2.0:
1. Reinstall Release 2.0. For installation instructions, see Section 3, Installing
NonStop SQL/MX.
2. If you compiled Release 2.0 applications from the Release 2.1 environment, you
must recompile them after you fall back from Release 2.0.
3. If you compiled user modules from Release 2.1, you must recompile them after
you fall back from Release 2.0. Recompile all user modules that were compiled
after Release 2.1 was installed.
Preparing to Fall Back From Release 2.1 or
Release 2.0 to Release 1.8
If you migrate from Release 1.8 to Release 2.1 or Release 2.0, you can use the
fallback procedure in Falling Back From Release 2.1 or Release 2.0 to Release 1.8 on
page A-4. Falling back to an SQL/MX release earlier than Release 1.8 is not
supported.
The complexity associated with falling back to Release 1.8 varies depending on the
amount of work performed under Release 2.1 or Release 2.0:
•
You did not make any changes.
If the only work you performed from Release 2.1 or Release 2.0 was to migrate the
metadata and then run existing Release 1.8 applications, falling back to Release
1.8 is straightforward. Before you reinstall a previous RVU, used the DROP SQL
command to uninstall the Release 1.8 metadata that you migrated to Release 2.1
or Release 2.0. After you reinstall the Release 1.8 RVU, no other changes are
required.
•
You recompiled user module files only.
If the only changes you made under Release 2.1 or Release 2.0 were
recompilations of user module files using the SQL/MX compiler, you must
recompile these module files with the Release 1.8 compiler after falling back.
•
You made changes to metadata tables.
If you changed any MPALIAS, DEFAULTS, PROCS, PARAMS, or ODBC
metadata tables (for example, to add a new MPALIAS) and you want to retain