SQL/MX 3.1 Installation and Management Guide (H06.23+, J06.12+)

Managing an SQL/MX Distributed Database
HP NonStop SQL/MX Release 3.1 Installation and Management Guide—663852-001
13-26
Managing Mixed Versions of NonStop SQL/MX

Running different versions of SQL/MX software simultaneously on separate nodes
of an interrelated SQL/MX database application is not allowed between SQL/MX
Release 3.x nodes and SQL/MX Release 2.x nodes.

Running a later version of SQL/MX software on a development node that supports
a production node or nodes running an earlier version of SQL/MX software is not
allowed between SQL/MX Release 3.x nodes and SQL/MX Release 2.x nodes.

Upgrading to a later version of SQL/MX or downgrading to an earlier version is
allowed.

After upgrading a node from SQL/MX Release 2.x to SQL/MX Release 3.1, you
must recompile all the existing embedded modules for compatibility with the
enhanced SQL/MX Release 3.1 executor.

SQL/MX Release 3.1 supports Application Migration Without Recompilation
(AMWR). After migrating applications from SQL/MX Release 3.0 to SQL/MX
Release 3.1, you can do the following:

Execute the user modules and SQL queries compiled in SQL/MX Release
3.0 without any change.

Use the RCBs generated on SQL/MX Release 3.0 without any change.
Also, you do not need to run
mxtool fixrcb.
However, after downgrading a node from SQL/MX Release 3.1 to SQL/MX
Release 3.0, all the query plans and modules must be recompiled.
You can use different SQL/MX software versions if the versions are within the
supported range, and SQL/MX Release 3.1 nodes, SQL/MX Release 3.0 nodes, and
SQL/MX Release 2.x nodes do not interoperate in the same distributed network with
each other. For more information, see The SQL/MX Environment
on page 1-11.