SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide (H06.22+, J06.11+)

Falling Back to SQL/MX Release 2.x
HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide—666210-002
5-7
Installing SQL/MX 2.x
This command regenerates RCBs for SQL/MX objects in all catalogs that were
originally created on the system.
If the system fallback is performed for a clustered or networked environment, you must
fall back all affected systems simultaneously and must run the
mxtool fixrcb
command on each involved system.
To verify the database recoverability after a system fallback, you must take a full set of
online dumps after executing the
mxtool fixrcb command successfully. For more
information on the
mxtool fixrcb command, see MXCI Commands in the SQL/MX
Reference Manual.
Installing SQL/MX 2.x
1. Install SQL/MX 2.x. For information on installing SQL/MX Release 2.x, see
Installing NonStop SQL/MX in the
SQL/MX Installation and Management Guide.
2. Perform the operations described in Migrating Applications after System Fallback
.
Migrating Applications after System Fallback
The modules that were generated on SQL/MX Release 3.0 are no longer compatible
after a system fallback to an earlier release. Therefore, all such modules must be
recompiled after system fallback.
An alternate method is to save a copy of the modules before system upgrade and then
reinstate that copy after fallback. This method is applicable only if the database layout
after the fallback is similar to the layout before the system upgrade.
Changes Required After Falling Back
Falling back might require changes to some or all of these corequisite product
versions, particularly if you fall back to an earlier RVU:

RDF (Independent Product)

NonStop Server for Java (Independent Product)

JDBC Driver for SQL/MX (Independent Product)

DP2

TMF

Measure

Backup and Restore 2
For more information, see the
H06.nn or J06.nn Release Version Update
Compendium
.