SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Migrating an SQL/MP Database to NonStop SQL/MX
Release 2.1 or Release 2.0
HP NonStop SQL/MX Installation and Management Guide—523723-004
14-5
Using the migrate Utility to Migrate SQL/MP
Metadata From Release 1.8
2. Use the procedures in Section 3, Installing NonStop SQL/MX to install Release 2.1
or Release 2.0 on nodes where the SQL/MP database resides.
3. Create the target database. For more information, see Section 7, Creating an
SQL/MX Database. Note that you can use the SHOWDDL command to display the
SQL/MX syntax of an SQL/MP table. For more information about SHOWDDL, see
the SQL/MX Reference Manual.
4. Use one of the tools or methods in Tools for Migrating Data on page 14-15 to
transfer data from SQL/MP tables into the target database.
Using the migrate Utility to Migrate SQL/MP
Metadata From Release 1.8
Use the migrate utility to migrate metadata from a Release 1.8 environment to
Release 2.1 or Release 2.0. The migrate utility copies metadata from Release 1.8
metadata tables to Release 2.1 or Release 2.0 metadata tables. Table 14-1 identifies
these metadata tables.
The migrate utility migrates SQL/MP aliases from the MPALIAS table, system
defaults from the DEFAULTS table, stored procedures in Java (SPJs) from the PROCS
Table 14-1. Source and Destination Metadata Tables for Metadata Migration
From Release
1.8 Metadata
Table To Release 2.1 or Release 2.0 Metadata Table or Tables
MPALIAS cat.DEFINITION_SCHEMA_VERSION_vernum.MP_PARTITIONS and
cat.DEFINITION_SCHEMA_VERSION_vernum.OBJECTS
*
DEFAULTS NONSTOP_SYSTEM_NSK.SYSTEM_DEFAULTS_SCHEMA.SYSTEM_
DEFAULTS
ZONAM2ID NONSTOP_SQLMX_node.MXCS_SCHEMA.NAME2ID
ZOAS2DS NONSTOP_SQLMX_node.MXCS_SCHEMA.ASSOC2DS
ZODS NONSTOP_SQLMX_node.MXCS_SCHEMA.DATASOURCES
ZOENV NONSTOP_SQLMX_node.MXCS_SCHEMA.ENVIRONMENTVALUES
ZORES NONSTOP_SQLMX_node.MXCS_SCHEMA.RESOURCEPOLICIES
PROCS cat.DEFINITION_SCHEMA_VERSION_vernum.OBJECTS and
cat.DEFINITION_SCHEMA_VERSION_vernum.ROUTINES and
cat.DEFINITION_SCHEMA_VERSION_vernum.TEXT
PARAMS cat.DEFINITION_SCHEMA_VERSION_vernum.COLS
* cat is the relevant catalog name for the object. An object with an SQL/MP alias of
CAT.SCH.TI will have its alias migrated to
CAT.DEFINITION_SCHEMA_VERSION_vernum.OBJECTS, while an object with an SQL/MP
alias of CAT1.SCH.TI will have its alias migrated to
CAT1.DEFINITION_SCHEMA_VERSION_vernum.OBJECTS.