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
Fallback sequence
Based on your requirements, you can fall back in one of the following ways:
• If you have not upgraded the metadata to SQL/MX Release 3.2 and have not created any
new databases, you can fall back as shown in Figure 11 (page 48).
Figure 11 The v3100, v3000 or v1200 objects are not upgraded and new objects are not created
on SQL/MX Release 3.2
Start
Stop Applications
Stop TMF, Start, Stop TMF
Install desired fallback release,
including required fallback SPRs if any
Run mxtool fixrcb
Recompile Applications
Install 2.X, if required
Starting Version
v1200
OR
v3000
OR
v3100
cat1
Sch1
App1
Resulting Version
v3100
OR
v3000
OR
v1200
cat1
Sch1
App1
Final Version
v1200
cat1
Sch1
App1
48 Falling back from SQL/MX Release 3.2