SQL/MX 3.2 Installation and Upgrade Guide (H06.25+, J06.14+)
Table Of Contents
- HP NonStop SQL/MX Release 3.2 Installation and Upgrade Guide
- Contents
- About this manual
- 1 Preparing to install SQL/MX
- 2 Installing SQL/MX
- Summary of installation tasks
- Preinstallation tasks
- Using the InstallSqlmx script
- Installing SQL/MX
- Verifying the SQL/MX installation
- Post-Installation tasks
- 3 Installing a sample database
- 4 Overview of SQL/MX system upgrade
- 5 Considerations for upgrading the system to SQL/MX Release 3.2
- 6 Upgrading the system to SQL/MX Release 3.2
- 7 Falling back from SQL/MX Release 3.2
- A Removing security administrator grants
- B Identifying tables that contain an IDENTITY Column
- C Identifying tables where the ownership has changed
- D Version management and interoperability
- SQL/MX releases
- Interoperability of SQL/MX releases
- Versions of SQL/MX software components
- E Conversions
- Index
Table 5 (page 63) lists the current supported RVUs of NonStop systems and the SQL/MX release
that they support. You can install only one SQL/MX release on a system at a time.
Table 5 RVUs and Supported SQL/MX Releases
Supported SQL/MX ReleasesRVUs
SQL/MX Release 3.2H06.25 and later
nl
J06.14 and later
Interoperability of SQL/MX releases
SQL/MX Release 3.2 does not interoperate with other versions of SQL/MX in an EXPAND network.
All interoperating systems in the EXPAND network must have SQL/MX Release 3.2 software
installed.
Versions of SQL/MX software components
Each SQL/MX software component and persistent entity has a version identifier that identifies its
software release and that can be understood by other SQL/MX releases. Versioned software
components include the SQL/MX system software version (MXV).
Versioned persistent entities, which persist over time and across releases, include:
• Schemas that contain SQL/MX database objects.
• SQL/MX database objects, such as tables, views, and indexes.
• Compiled modules.
SQL/MX uses version identifiers to determine if a software component or persistent entity is
compatible with the SQL/MX release. Before using a software component or operating on a
persistent entity, SQL/MX checks the version identifier of the software component or persistent
entity. If the version identifier is compatible with the SQL/MX release, SQL/MX successfully proceeds
with the operation. If the version identifier is incompatible with the SQL/MX release, SQL/MX fails
the operation and returns a versioning error indicating an incompatibility.
The use of version identifiers enables interoperability between compatible versions and prevents
interoperability between incompatible versions. For more information, see:
• “Software requirements” (page 12)
• “Verifying correct versions of independent software products” (page 13)
• “Starting TMF” (page 13)
• “SQL/MX Release Information for H-Series RVUs” (page 17)
Version identification of SQL/MX software components
All version identification in SQL/MX is numeric. General availability (GA) and Controlled Availability
(CA) software releases are assigned version numbers that are multiples of 20. General and
controlled availability releases do not interoperate with Early Adopter Program (EAP) releases or
other releases whose version numbers are not multiples of 20. The following table lists the software
version identifiers for SQL/MX Release 3.2.
Interoperability of SQL/MX releases 63