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-14
Steps for Migrating SPJs From Release 1.8 to
Release 2.1 or Release 2.0
Steps for Migrating SPJs From Release 1.8 to Release 2.1 or
Release 2.0
When you run the PRELIMINARY REPORT command, the migrate utility might
report that these items do not exist on the Release 2.1 or Release 2.0 system:
•
TANDEM_SYSTEM_node.SYSTEM_SQLJ_SCHEMA schema
•
Internal class file in mxlangman.jar
You can ignore these messages and continue the migration process. The
NONSTOP_SQLMX_node.SYSTEM_SQLJ_SCHEMA schema and internal class file should
already be part of Release 2.1 or Release 2.0 if you installed it correctly. Do not create
the TANDEM_SYSTEM_node.SYSTEM_SQLJ_SCHEMA schema in a Release 2.1 or
Release 2.0 database.
For instructions on how to migrate metadata for SPJs from Release 1.8 to Release 2.1
or Release 2.0 using the migrate utility, see the SQL/MX Guide to Stored Procedures
in Java.
Migrating an Enscribe Database to Release 2.1
or Release 2.0 Using SQL/MX Tables
To read Enscribe files into SQL/MX tables, use the DataLoader/MX product. By
default, DataLoader/MX does not perform data transformations. For Enscribe files with
simple data types (for example, INTEGER or CHARACTER formats), use these steps:
1. To load the Enscribe data into DataLoader/MX, run DataLoader/MX with the
Enscribe file as the input and $RECEIVE as the output. For more information about
running DataLoader/MX, see the DataLoader/MX Reference Manual.
2. To load the DataLoader/MX data into a SQL/MX table, run import with input from
the DataLoader/MX process and a properly configured format file. For more
information about running import, see the SQL/MX Reference Manual.
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.