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
4 Overview of SQL/MX system upgrade
This section introduces the process of upgrading the system to SQL/MX Release 3.2 and discusses
the following topics:
• “Terminology” (page 30)
• “Upgrading SQL/MX system” (page 30)
• “Guidelines for conducting the system upgrade” (page 31)
• “Assistance with upgrade” (page 31)
Terminology
You must be familiar with the following terms, which are used throughout the manual:
Metadata Downgrade or DOWNGRADE. A user-initiated operation that transforms metadata from
one version to a lower version.
Metadata Upgrade or UPGRADE. A user-initiated operation that transforms metadata from one
version to a higher version.
Migration. Migrating applications from an older version to a newer SQL/MX release version.
SQL/MX application. Uses SQL/MX syntax, is SQL-compiled using MXCMP, and can query SQL/MP,
SQL/MX database objects, JDBC/MX, and ODBC.
SQL/MX Release 2.x. SQL/MX Release 2.0, SQL/MX Release 2.1, SQL/MX Release 2.2, and
subsequent releases until otherwise indicated in a replacement publication.
SQL/MX Release 3.x. SQL/MX Release 3.0, SQL/MX Release 3.1, SQL/MX Release 3.2 and
subsequent releases unless otherwise specified.
Release Upgrade. A user-initiated operation that replaces an older version software with a newer
version. For example, you upgrade to a newer incremental or maintenance release of SQL/MX,
such as upgrading from SQL/MX Release 2.3.x to SQL/MX Release 3.1.
Release. A set of interdependent software products that are distributed together.
Version. A number that identifies the capabilities of a release. A given release has only one version
whereas a given version can be assigned to more than one release. For example, "v1200" means
"version 1200", "v3200" means "version 3200".
Upgrading SQL/MX system
If the system upgrade can be broken into phases, each phase must include its own complete plan:
For more information, see...Upgrade Plan
• “Upgrading the system to SQL/MX Release 3.2” (page 37)
Plan for migrating applications
• “Falling back from SQL/MX Release 3.2” (page 46)
Plan for fallback
• SQL/MX Management Manual
Plan for updating disaster recovery or
RDF configuration and procedures
• “Guidelines for conducting the system upgrade” (page 31)
Plan for validating that upgrade is
successful
30 Overview of SQL/MX system upgrade