SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)

Preparing to Migrate From SQL/MX Release 1.8 to
SQL/MX Release 2.x
HP NonStop SQL/MX Database and Application Migration Guide540435-005
5-5
Preparing to Migrate Applications
Preparing to Migrate Applications
Planning activities for migrating applications depend on your environment and the
types of applications you are currently using. After metadata migration, some SQL/MX
applications run unchanged in the SQL/MX Release 2.x environment. However, others
require recompiling. If SQL/MX tables are created in that environment, applications
must be rewritten and recompiled to access the new tables. Before migrating to
SQL/MX Release 2.x, see Section 7, Migrating SQL/MX Release 1.8 Applications to
SQL/MX Release 2.x.
Planning to Migrate Other Nodes in the
Network
In multinode installations, where queries must access data on other nodes, all SQL/MX
Release 1.8 nodes must migrate to SQL/MX Release 2.x at the same time. Nodes
running SQL/MX Release 1.8 and SQL/MX Release 2.x cannot interoperate. For more
information, see Interoperability of NonStop SQL/MX Releases
on page 2-8.
Steps for Migrating From SQL/MX Release 1.8
to SQL/MX Release 2.x
To migrate from SQL/MX Release 1.8 to SQL/MX Release 2.x:
1. Plan for migration as described in this section.
2. Use the procedures in the
SQL/MX Installation and Management Guide to install
SQL/MX Release 2.x on nodes where SQL/MX Release 1.8 resides.
3. Create SQL/MX user catalogs and schemas for the SQL/MP aliases and stored
procedures in Java (SPJs) that you plan to migrate.
4. Use the
migrate utility to migrate SQL/MP metadata for system defaults, SQL/MP
aliases, ODBC/MX, and SPJs to SQL/MX system metadata tables. See Section 6,
Migrating SQL/MP Metadata From SQL/MX Release 1.8 to SQL/MX Release 2.x.
5. Resolve application migration issues. See Section 7, Migrating SQL/MX Release
1.8 Applications to SQL/MX Release 2.x.