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-8
Steps for Migrating MPALIAS Metadata From
Release 1.8 to Release 2.1 or Release 2.0
Steps for Migrating MPALIAS Metadata From Release 1.8 to
Release 2.1 or Release 2.0
These steps assume that you have upgraded a Release 1.8 environment to Release
2.1 or Release 2.0 and that the MPALIAS table resides on the same node as Release
2.1 or Release 2.0:
1. In an SQLCI session, enter the GET CATALOG OF SYSTEM command to display
the volume and subvolume of the SQL/MP system catalog where the MPALIAS
table resides:
GET CATALOG OF SYSTEM;
2. In the OSS environment, set these environment variables for the volume and
subvolume of the SQL/MP system catalog:
export SQLMX_NAMETYPE=NSK
export NSK_VOL=\$vol
export NSK_SUBVOL=subvol
vol and subvol are the names of the volume and subvolume where the
MPALIAS table resides.
3. To determine which entries in the MPALIAS table to migrate, use the SHOW
MPALIAS command of the migrate utility and direct this information to a file:
/usr/tandem/sqlmx/bin: migrate SHOW MPALIAS >
mpalias_info.out
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.
Note. The migrate utility runs only on the OSS command line and is case-sensitive.