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-6
System Requirements for Migrating SQL/MP
Metadata
and PARAMS tables, and ODBC metadata from the ZOAS2DS, ZODS, ZOENV,
ZONAME2ID, and ZORES tables. It copies this metadata to the Release 2.1 or
Release 2.0 metadata tables identified in Table 14-1 on page 14-5. The catalog-name
(cat) prefix provided with the DEFINITION_SCHEMA tables identifies the catalog in
which the DEFINITION_SCHEMA table resides.
System Requirements for Migrating SQL/MP Metadata
•
You have migrated a Release 1.8 environment to Release 2.1 or Release 2.0.
•
Release 2.1 or Release 2.0 is installed and running on the system.
•
The Transaction Management Facility (TMF) is installed and running on the
system.
•
The SQL/MP metadata tables reside in the SQL/MP environment on the same
node as Release 2.1 or Release 2.0.
•
The target catalogs and schemas for MPALIAS, PROCS, and PARAMS exist in the
system metadata of the Release 2.1 or Release 2.0 database.
•
You are the super ID and have access to tables that contain the SQL/MP
metadata. Only the super ID can run the migrate utility.
Before Migrating SQL/MP Metadata
Before you use the migrate utility to migrate SQL/MP metadata from Release 1.8 to
Release 2.1 or Release 2.0, you must perform these tasks:
1. Create the user catalogs and schemas in the Release 2.1 or Release 2.0 database
that are required when you migrate SPJs and SQL/MP aliases. See Table 14-1 on
page 14-5 for naming guidelines.
2. Use the migrate utility immediately after you have installed Release 2.1 or
Release 2.0. For more information, see Installing NonStop SQL/MX on page 3-3.
3. In your migrate commands, always put quotation marks around reserved words,
including “SQL.”
Note. Before you use the migrate utility:
•
Create the user catalogs and schemas in the Release 2.1 or Release 2.0 database. For
catalog and schema naming guidelines, see the SQL/MX Reference Manual. The user
catalogs and schemas are required to migrate SPJs and SQL/MP aliases from Release
1.8 to Release 2.1 or Release 2.0. If you do not create the user catalogs and schemas,
migrate returns error messages reporting that they do not exist, and the CREATE
MPALIAS and CREATE PROCEDURE statement portion of the utility fails.
•
Install Release 2.1 or Release 2.0 as described in Installing NonStop SQL/MX on
page 3-3, and then immediately run the migrate utility. Until you run the migrate utility,
your SQL/MP aliases and Release 1.8 defaults entries and SPJs will not work in the
Release 2.1 or Release 2.0 environment.