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-2
System Requirements for Migrating SQL/MP
Metadata
System Requirements for Migrating SQL/MP
Metadata
•
You have migrated from SQL/MX Release 1.8 to SQL/MX Release 2.x by installing
the G06.23 or later RVU and SQL/MX Release 2.x on the system.
•
The HP NonStop Transaction Management Facility (TMF) is installed, configured,
and running on the system.
•
The SQL/MP metadata tables reside in the SQL/MP environment on the same
node as SQL/MX Release 2.x.
•
You can access the target catalogs and schemas for the SQL/MP aliases and
SPJs, meaning that the catalogs either exist on the node or have been registered
on the node in the SQL/MX Release 2.x system metadata.
•
You are the super ID, which has access to tables that contain the SQL/MP
metadata. Only the super ID can run the
migrate utility.
Steps Before Migrating SQL/MP Metadata
Before using the migrate utility to migrate SQL/MP metadata from SQL/MX Release
1.8 to SQL/MX Release 2.x, perform these tasks:
1. Install SQL/MX Release 2.x as described in the
SQL/MX Installation and
Management Guide.
2. Create user catalogs and schemas in the SQL/MX Release 2.x database. For
catalog and schema naming guidelines, see the
SQL/MX Reference Manual.
The user catalogs and schemas must exist before you can migrate the metadata of
SPJs and SQL/MP aliases from SQL/MX Release 1.8 to SQL/MX Release 2.x. If
you do not create the user catalogs and schemas,
migrate returns error
messages reporting that the catalogs and schemas do not exist, and the CREATE
SQLMP ALIAS and CREATE PROCEDURE portion of the utility fails.
Until you run the
migrate utility, your SQL/MP aliases, system defaults, ODBC/MX
(MXCS) metadata, and SPJs will not work in the SQL/MX Release 2.x environment.
Note. Choose the catalogs and schemas carefully. If you specify incorrect catalogs and
schemas during migration and migration succeeds, you must use the ALTER SQLMP
ALIAS statement (for SQL/MP aliases) and the CREATE PROCEDURE and DROP
PROCEDURE statements (for SPJs) to rename the catalogs and schemas in the SQL/MX
system metadata.