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-5
Upgrading from SQL/MX Release 3.0 to SQL/MX
Release 3.1
SQL/MX Release 3.1 enables upgrading of applications from an SQL/MX Release
2.3.x system to a SQL/MX Release 3.1 system without requiring you to recreate and
reload the database. You do not need to preprocess, compile the host language, and
link when you migrate from SQL/MX Release 2.3.x to SQL/MX Release 3.1. However,
SQL/MX Release 3.1 does not support user modules and query plans from SQL/MX
2.3.x or earlier versions. You must to recompile all the existing embedded modules so
they can be compatible with the enhanced SQL/MX Release 3.1 executor.
After installing SQL/MX Release 3.1, you must reformat the RCBs for all database
objects and recompile all embedded modules before accessing the database. After
reformatting the RCBs, you can retain the existing SQL/MX Release 2.3.x metadata
(v1200) that is in use or upgrade all v1200 metadata to SQL/MX Release 3.1 (v3100).
After a system fallback, before accessing the database, you must reformat the RCBs
for all database objects. You might need to preprocess, compile, and link when you fall
back from SQL/MX Release 3.1. The Fallback SPR is provided for SQL/MX Release
2.3.4 (ANC SPR on H06.21). To fall back to an earlier release of SQL/MX 2.x, you
must perform the fallback in the following sequence:
1. Fall back to SQL/MX Release 2.3.4.
2. Fall back to the required SQL/MX 2.x version.
Upgrading from SQL/MX Release 3.0 to
SQL/MX Release 3.1
This section describes the sequence and the procedures to upgrade from SQL/MX
Release 3.0 to SQL/MX Release 3.1.

Upgrade sequence on page 4-6

Preinstallation on page 4-6

Installing SQL/MX Release 3.1 on page 4-7

Accessing the database on page 4-7

Migrating the database after system upgrade on page 4-7

Migrating applications after system upgrade on page 4-7
Note. Recompiling programs might result in different execution plans, causing a change in
performance.
Note. SQL/MX Release 2.3.x metadata (v1200) for existing applications and data objects in
existing catalogs can coexist on a single system with SQL/MX Release 3.1 metadata (v3100)
for objects in newly created catalogs. To use version 3100 metadata for existing objects, you
must upgrade all existing v1200 metadata and recompile the embedded applications.