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

HP NonStop SQL/MX Database and Application Migration Guide—540435-005

4-1

Falling Back to an Earlier Version of

SQL/MX Release 2.x

This section describes falling back from a newer version of SQL/MX Release 2.x, such

as SQL/MX Release 2.2, to an earlier version of SQL/MX Release 2.x, such as

Release 2.1 or 2.0. To fall back to SQL/MX Release 1.8, see Part II, Migrating From

SQL/MX Release 1.8 to SQL/MX Release 2.x.

If you encounter a serious problem with SQL/MX Release 2.x and decide you need to

fall back to a previous version of SQL/MX Release 2.x, read this section carefully and

understand it fully before attempting the fallback procedure.

This section addresses these topics:

•

Fallback Considerations on page 4-1

•

Steps for Falling Back SQL/MX Release 2.x on page 4-1

•

Changes Required After Falling Back on page 4-2

Fallback Considerations

•

To ensure a successful fallback, you might need to install certain SPRs before

attempting to fall back. For more information, see the

H06.nn or G06.nn Release

Version Update Compendium and the Readme file for the RVU to which you would

fall back.

•

Applications that you compiled with the SQL/MX Release 2.2 compiler need to be

recompiled with the previous release of the SQL/MX compiler (SQL/MX Release

2.1 or SQL/MX Release 2.0) after fallback.

•

Applications that you compiled with the SQL/MX Release 2.1 compiler need to be

recompiled with the previous release of the SQL/MX compiler (SQL/MX Release

2.0) after fallback.

Steps for Falling Back SQL/MX Release 2.x

If you upgrade to a newer version of SQL/MX Release 2.x, you might find it necessary

to fall back to an earlier version of SQL/MX Release 2.x. For example, you might need

to fall back from:

•

SQL/MX Release 2.2 to SQL/MX Release 2.1

•

SQL/MX Release 2.1 to SQL/MX Release 2.0

Note. If you encounter the problem when using new features that are specific to SQL/MX

Release 2.x, consider discontinuing the use of those features instead of falling back from that

database environment.