SQL/MX 3.1 Database and Application Migration Guide (H06.23+, J06.12+)

Contents
HP NonStop SQL/MX Release 3.1 Database and Application Migration Guide—663853-001
iii
A. Removing Security Administrator Grants
Stopping TMF 5-7
Installing SQL/MX Release 3.0 5-8
Installing SQL/MX Release 2.3.4 5-8
Accessing the database 5-8
Installing SQL/MX Release 2.x 5-9
Migrating applications after system fallback 5-9
Changes required after falling back 5-9
A. Removing Security Administrator Grants
B. Identifying Tables That Contain an IDENTITY Column
C. Identifying tables where the ownership has changed
Index
Figures
Figure 2-1. Migration Path from SQL/MX 2.3.x or SQL/MX 3.0 to SQL/MX 3.1 2-1
Figure 2-2. Compatibility of SQL/MX releases in a network 2-2
Figure 2-3. Compatibility of SQL/MX releases in a network after migration 2-2
Figure 4-1. Sequence to upgrade from SQL/MX 2.3.x to SQL/MX 3.1 4-2
Figure 4-2. Sequence to upgrade from SQL/MX 3.0 to SQL/MX 3.1 4-6
Figure 4-3. Using new features of SQL/MX Release 3.1 on existing databases 4-8
Figure 4-4. Coexistence of new and old databases 4-9
Figure 4-5. New features of SQL/MX Release 3.1 not required 4-9
Figure 5-1. Falling Back from SQL/MX 3.1 to SQL/MX 2.3.4 or SQL/MX 3.0 5-1
Figure 5-2.
Falling back to a SQL/MX 2.x version earlier than SQL/MX 2.3.4 5-2
Figure 5-3. The v3000 or v1200 objects are not upgraded and new objects are not
created on SQL/MX 3.1 5-3
Figure 5-4.
New database objects are created on SQL/MX Release 3.1 5-4
Figure 5-5.
The v1200 or v3000 objects are upgraded to v3100 5-5
Tables
Table 3-1. SQL/MX Releases on Systems Running H-Series or J-series
RVUs 3-2
Table 3-2. RVUs and Supported SQL/MX Releases 3-6
Table 3-3. Software Version Identifiers for SQL/MX Release 3.1 3-8