SQL/MX 3.2.1 Installation and Upgrade Guide (H06.26+, J06.15+)

What this manual does not cover
• Migration from SQL/MP to SQL/MX. For more information, see the SQL/MP to SQL/MX
Database and Application Migration Guide.
• Migration from other database vendors to SQL/MX. For assistance, contact your service
provider. For more information, see “Assistance with upgrade” (page 31).
• Migration of SQL/MX, SQL/MP, and Enscribe databases and applications from an NonStop
S-series system to an Integrity NonStop NS-series system. For more information, see the NonStop
NS-Series Database Migration Guide.
• Migration from Enscribe databases and applications to SQL/MX. An automated tool to convert
Enscribe databases and applications to SQL/MX does not exist. The Escort SQL product
converts Enscribe databases and applications to NonStop SQL/MP. For more information,
see the ESCORT SQL™ User’s Guide, which you can obtain from Carr Scott Software Inc. at
http://www.carrscott.com/evaluation_prog.shtml. If there is sufficient market demand, Carr
Scott Software Inc. might consider modifying Escort SQL to support direct Enscribe-to-SQL/MX
migrations. If you or your customer deems this functionality to be critical to your project, send
a note and background on the project to [e-mail].
• Migration to format 2 SQL/MP tables. For more information, see the SQL/MP Installation and
Management Guide.
Document organization
This document is organized as follows:
Describes pre-installation requirements.“Preparing to install SQL/MX” (page 12)
Describes the steps for installing SQL/MX.“Installing SQL/MX” (page 14)
Describes the steps for installing the SQL/MX sample
database.
“Installing a sample database” (page 28)
Defines upgrade terminology, provides planning
considerations, and describes where you can go for further
assistance.
“Overview of SQL/MX system upgrade” (page 30)
Discusses the factors that you must consider before
upgrading to SQL/MX Release 3.2.x.
“Considerations for upgrading the system to SQL/MX
Release 3.2.x” (page 33)
Describes SQL/MX releases, interoperability of SQL/MX
releases, versions of SQL/MX software components, query
plan versioning, and managing a mixed-node network.
“Version management and interoperability” (page 60)
Provides guidelines for upgrading to SQL/MX Release
3.2.x.
“Upgrading the system to SQL/MX Release 3.2.x”
(page 37)
Provides guidelines for downgrading to an earlier version
of SQL/MX.
“Falling back from SQL/MX Release 3.2.x” (page 46)
Provides example steps for removing any Security
Administrator grants prior to falling back to an earlier
release of SQL/MX.
“Removing security administrator grants” (page 55)
Provides example steps for removing any identifying tables
that contain an IDENTITY column as an aid to falling back
to an earlier release of SQL/MX.
“Identifying tables that contain an IDENTITY Column”
(page 58)
Provides examples to identify the list of objects in a catalog
whose owners are different from their parent schema
“Identifying tables where the ownership has changed”
(page 59)
owners, and the steps to change the ownership of those
objects.
What this manual does not cover 9