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-5
Preinstallation

Applications that are compiled using the SQL/MX Release 3.0 compiler need to be
pre-processed, recompiled, and linked with an earlier release of the SQL/MX
compiler after the fallback.

The online dumps taken on SQL/MX Release 3.0 cannot be used by TMF recovery
on SQL/MX Release 2.x. HP recommends that you take new full TMF online
dumps immediately after fallback.
Preinstallation
You must complete the following steps before installing SQL/MX 2.x:

Migrating the Database for System Fallback

Stopping TMF
Migrating the Database for System Fallback
The DOWNGRADE utility facilitates system fallback from SQL/MX Release 3.0 to
SQL/MX Release 2.3.4.
Consider the following scenarios for system fallback:

All schemas on the system are version 1200. In this case, the DOWNGRADE utility
is not required.

New database features are not used in version 3000 schemas. You can run a
downgrade all metadata command to downgrade the metadata to version
1200 as follows:
>> downgrade all metadata to version 1200;

New database features are used for some objects in version 3000 schemas. In this
case, do the following:

Use the FEATURE_VERSION_INFO function to obtain the name and object
type of database objects that use new features. Such objects prevent a
downgrade to version 1200. For more information, see SQL/MX Functions and
Expressions in the
SQL/MX Reference Manual.

Convert the old unsupported objects to corresponding copy objects without
new features.

Drop the old unsupported objects before the system downgrade.

Retry the downgrade operation.
Note. Recompiling programs may result in different execution plans leading to a change in
performance.