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
1. The first number indicates a major release, which introduces major new functionality and a
new SQL version.
2. The second number indicates an incremental release, which introduces an incremental change
and some new functionality.
3. The third number indicates a maintenance release, which introduces bug fixes and minimal
new functionality.
The upgrade risk increases from maintenance to major releases because major releases introduce
significant new functionality that makes fallback more difficult, if implemented.
The first and second levels of the release name (for example, SQL/MX Release 3.0) are based on
the product version identifier (for example, H30). Major and incremental releases typically change
the product version of SQL/MX. Maintenance releases and time-critical fixes (TCFs) do not change
the product version of SQL/MX.
Major and incremental releases
Major releases introduce significant new functionality. These releases occur less frequently and
usually require you to take specific action to use the new functionality, such as perform an upgrade
operation or alter existing applications.
Incremental releases introduce incremental changes and some new functionality.
In this manual, the SQL/MX releases are identified by major and incremental release numbers
such as SQL/MX Release 2.3.4 and SQL/MX Release 3.2.
Maintenance releases
Maintenance releases introduce bug fixes and minimal new functionality. These releases occur
most frequently and rarely affect all the component products in the SQL/MX product set.
SQL/MX product T-Numbers and VPROC information
In a given SQL/MX release, participating SQL/MX products include the product version identifier
in their T-numbers (for example, T1051H30).
The VPROC information of each SQL/MX product in a given release is:
TNNNNPNN_DDMMMYYYY_SPR_RRR_MMDD
where:
TNNNNPNN
is the product T-number (for example, T1051) and the product version identifier
(PNN). The first letter P in PNN represents the RVU series to which the product version
applies:
• H for HP Integrity NS-series systems, which run H-series RVUs.
• J for HP Integrity NonStop™ BladeSystems, which run J-series RVUs.
The next two digits NN represent the SQL/MX release number (for example, 30 for
SQL/MX Release 3.0).
DDMMMYYYY
is the VPROC date (for example, 14FEB2011).
SPR
is the three-digit SPR identifier of the release (for example, ACF). For an initial PVU,
this field is the same as the product version PNN (for example, H30).
RRR
is the three-digit SQL/MX release number (for example, 300 for SQL/MX Release
3.0.0).
SQL/MX releases 61