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-7
Installing SQL/MX Release 3.1
2. Stop the HP NonStop Transaction Monitoring Facility (TMF).
Installing SQL/MX Release 3.1
For information on how to install SQL/MX Release 3.1, see Installing SQL/MX Release
3.1 on page 4-3.
Accessing the database
After the initial system load on the target release, the database is ready for use.
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 previous releases of SQL/MX (v1200 schemas, v3000
schemas) are supported.
An upgrade of older version metadata (v1200 schemas, v3000 schemas) to v3100
is supported.
v3100 schemas in new catalogs are supported without having to upgrade existing
metadata.
New SQL/MX Release 3.1 features are supported with v3100 metadata only. They
are not supported in v1200 or 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 that 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 or 3000.
Migrating applications after system upgrade
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:
Note. When upgrading from SQL/MX Release 3.0 to SQL/MX Release 3.1, you do not have to
stop TMF twice before the installation.
Note. When upgrading from SQL/MX Release 3.0 to SQL/MX Release 3.1, you do not have to
use the
mxtool fixrcb command, and recompile user application modules.
Note. A system that is upgraded from SQL/MX Release 3.0 might have v1200 schemas - or a
combination of v1200 and v3000 schemas - where that system previously was upgraded from
SQL/MX Release 2.3.x to SQL/MX Release 3.0, and no metadata upgrade was performed.