SQL/MX 3.2 Installation and Upgrade Guide (H06.25+, J06.14+)

Preinstallation
Before upgrading, complete the following steps:
1. Stop all applications that access the database.
2. Stop the HP NonStop Transaction Monitoring Facility (TMF).
NOTE: When upgrading from SQL/MX Release 3.0 or 3.1 to SQL/MX Release 3.2, you do not
have to stop TMF twice before the installation.
Installing SQL/MX Release 3.2
For more information about installing SQL/MX Release 3.2, see “Installing SQL/MX” (page 14) .
Accessing the database
After the initial system load on the target release, the database is ready for use.
NOTE: When upgrading from SQL/MX Release 3.0 or 3.1 to SQL/MX Release 3.2, you do not
have to use the mxtool fixrcb command, and recompile user application modules.
Upgrading the metadata after system upgrade
The following describes the SQL/MX Release 3.2 features and limitations related to an upgrade
of the metadata, which include physical data files and all related objects. For more information
on UPGRADE, see the SQL/MX Reference Manual.
• Databases created on previous releases of SQL/MX (v1200 schemas, v3000 schemas, v3100
schemas) are supported.
• An upgrade of older version metadata (v1200 schemas, v3000 schemas, v3100 schemas)
to v3200 is supported.
• v3200 schemas in new catalogs are supported without having to upgrade existing metadata.
• New SQL/MX Release 3.2 features are supported with v3200 metadata only. They are not
supported in v1200 or v3000 or v3100 schemas. For more information on how to use the
new SQL/MX Release 3.2 features, see “Upgrading the metadata and using new features on
existing and new databases” (page 44).
• 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 3200,
unless the CREATE_DEFINITION_SCHEMA_VERSION CQD is set to 1200 or 3000 or 3100.
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.
Similarly, a system that is upgraded from SQL/MX Release 3.1 might have any combination of
v1200, v3000 and v3100 schemas.
Migrating applications after system upgrade
SQL/MX Release 3.2 supports application migration without recompilation.
42 Upgrading the system to SQL/MX Release 3.2