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

Migrating SQL/MP Metadata From SQL/MX Release
1.8 to SQL/MX Release 2.x
HP NonStop SQL/MX Database and Application Migration Guide—540435-005
6-5
Steps for Migrating MPALIAS Metadata to SQL/MX
Release 2.x
4. Use the migrate SHOW SCRIPT command to generate a script file from which
you can fix discrepancies if they exist.
5. Edit the script file as needed to fix the discrepancies.
6. Use the
migrate EXECUTE command with the SCRIPT option to move entries
from specified SQL/MP metadata to SQL/MX metadata by executing the edited
script.
7. Examine and resolve errors in the error log file.
Steps for Migrating MPALIAS Metadata to
SQL/MX Release 2.x
To use SQL/MP aliases from SQL/MX Release 1.8 in SQL/MX Release 2.x, you must
migrate the metadata of the SQL/MP aliases. Use the
migrate utility to copy
metadata from the MPALIAS table in the SQL/MP environment to the
MP_PARTITIONS and OBJECTS tables in the SQL/MX environment.
These steps assume that you installed SQL/MX Release 2.x, that you created the
catalogs and schemas in the SQL/MX Release 2.x database, and that the MPALIAS
table resides on the same node as SQL/MX Release 2.x:
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;
Note the names of the volume and subvolume.
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.
Note. In your migrate commands, always put quotation marks around reserved words,
including “SQL.”
Note. Before migrating the metadata of SQL/MP aliases, create the user catalogs and
schemas in which to migrate them. For more information, see Steps Before Migrating SQL/MP
Metadata on page 6-2.
Note. The migrate utility runs only on the OSS command line and is case-sensitive.