SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide (H06.22+, J06.11+)
Overview of SQL/MX Migration
HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide—666210-002
1-2
Planning for Migration
compliance is increased for numeric to character conversions. The conversion of
numeric columns to character columns fails if truncation occurs. In SQL/MX
Release 2.x, truncation during conversion does not cause an error. You must
review and test applications for the presence of truncation. For more information,
see Conversions from numeric to char or varchar on page 2-7.
New Transaction Monitoring Facility (TMF) dumps are required to maintain data
integrity and to recover data. You must allot adequate time for this activity in the
migration schedule.
For more information, see the following:
Section 2, Considerations for upgrading to SQL/MX Release 3.0
Section 3, Version Management and Interoperability
Section 4, Upgrading to SQL/MX Release 3.0
Section 5, Falling Back to SQL/MX Release 2.x
Planning for Migration
You must save a copy of the modules before a system upgrade. If you fall back to the
current version at a later stage, you can reinstate this copy after fallback. This method
is applicable only if the database layout after the fallback is similar to the layout before
the system upgrade.
If the migration can be broken into phases, each phase should have its own complete
plan:
Guidelines for Conducting the Migration
To ensure a successful migration, follow these guidelines:
Conduct the Initial Migration in a Test Environment
Run Baseline Tests and Gather Data at Each Migration Phase
Assess the Success of the Migration
Migration Plan For more information, see...
Plan for migrating applications
Section 4, Upgrading to SQL/MX Release 3.0
Plan for fallback
Section 5, Falling Back to SQL/MX Release 2.x
Plan for updating disaster recovery or
RDF configuration and procedures
SQL/MX Installation and Management Guide
Plan for validating that migration is
successful
Guidelines for Conducting the Migration on
page 1-2










