SQL/MX 3.1 Database and Application Migration Guide (H06.23+, J06.12+)
Upgrading to SQL/MX Release 3.1
HP NonStop SQL/MX Release 3.1 Database and Application Migration Guide—663853-001
4-4
Migrating the database after system upgrade
An error might occur while running the mxtool fixrcb command due to one of the
following reasons:
An involved node has an incompatible version.
A user other than the local super ID performed the operation.
To verify the database recoverability after a system upgrade to SQL/MX Release 3.1,
you must take a full set of online dumps after executing the
mxtool fixrcb
command successfully.
Migrating the database after system upgrade
The following describes the SQL/MX Release 3.1 features and limitations related to
migration of the database, which includes physical data files and all related objects.
Databases created on SQL/MX Release 2.x (v1200 schemas) are supported.
An upgrade of v1200 schemas to v3100 is supported.
The v3100 schemas in new catalogs are supported without having to upgrade
v1200 metadata from SQL/MX 2.x version.
New SQL/MX Release 3.1 features are supported with v3100 metadata only. The
features are not supported in v1200 and v3000 schemas. For information on how
to use the new SQL/MX Release 3.1 features, see Upgrading the database and
using new features on existing and new databases on page 4-8.
New schemas in an existing, non-empty catalog will be of the same version as the
existing schemas in the catalog. The version of a new schema in an empty catalog
will be 3100, unless the
CREATE_DEFINITION_SCHEMA_VERSION CQD is set to
1200.
Migrating applications after system upgrade
Embedded SQL-based programs, ODBC and JDBC-based programs that use Module
File Caching (MFC) can create modules. The embedded modules that were generated
on SQL/MX Release 2.3.4 or earlier are no longer compatible. Therefore, all such
modules must be compiled after the system is upgraded to SQL/MX Release 3.1 and
before the applications are started.
Note. The FIXRCB operation does not handle the objects in catalogs that have a manual
reference on the local system. RCB fixup for objects in such catalogs must be performed on
the system where the automatic reference is located.
The FIXRCB operation is available on systems running J06.12 or later J-series RVUs, or
H06.23 or later H-series RVUs, and on fallback SPR (H06.21-ANC).
Note. Recovery on SQL/MX Release 3.1 by using pre-SQL/MX Release 3.1 TMF dumps has
some restrictions because of the changes made by
fixrcb. HP recommends that you take
new TMF online dumps when the SQL database is ready (after running
mxtool fixrcb).