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
SQL/MX successfully compiles and executes a query execution plan if the plan version is higher
than or equal to the earliest supported plan version and lower than or equal to the MXV of the
node where the plan is being executed. Otherwise, SQL/MX returns a versioning error.
Module versions
When you compile modules of embedded SQL/MX applications, the version assigned to a module
is the same as the current plan version of the node where you compiled the module. The SQL/MX
Release 3.2 compiler produces the v3200 modules.
For a module to be executed on a node, the module version must be higher than or equal to the
earliest supported plan version and lower than or equal to the MXV. Otherwise, SQL/MX generates
a versioning error.
NOTE: SQL/MX Release 3.2 supports v3200, v3100 and v3000 plans and modules. However,
it does not support SQL/MX Release 2.3.x plans and modules. Before executing SQL/MX Release
2.3.x plans and modules on SQL/MX Release 3.2, you must recompile only the modules.
Interoperability across schema versions
SQL/MX Release 3.2 is compatible with v1200 schemas, v3000 schemas, v3100 schemas, and
v3200 schemas, and the objects in such schemas on the local node and on remote compatible
nodes in a network.
Limitations to schema version interoperability
• Schemas of different versions cannot coexist in the same catalog.
• Immediately after upgrading from SQL/MX Release 2.3.x or from SQL/MX Release 3.0 or
3.1 to SQL/MX Release 3.2, the version of the system schema and all user schemas is either
1200 or 3000 or 3100. Executing the UPGRADE ALL METADATA command will upgrade
all metadata for the system schema and the user schemas to v3200. After the metadata is
upgraded to v3200, you cannot create v1200 schemas. However, using the control query
default (cqd) command, you can create v3000 schemas in catalogs that do not already
contain v3100 schemas:
control query default create_definition_schema_version '3000'
• Database relationships cannot cross schema versions.
For example, a view in a v1200 schema cannot reference a table in a v3100 schema.
The following types of database objects are able to establish cross schema relationships:
◦ views
◦ triggers
◦ RI constraints
If you attempt to establish cross-schema relationships between schemas of different versions,
the attempt will be rejected and an error is generated.
66 Version management and interoperability