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-7
Considerations for Falling Back From Release 2.1 or
Release 2.0
4. Use the SCRIPT option of the migrate EXECUTE command to move entries from
the specified SQL/MP metadata to the SQL/MX metadata by executing the edited
script.
Considerations for Falling Back From Release 2.1 or Release 2.0
You perform SQL/MP metadata migration as part of the database migration from
NonStop SQL/MP to Release 2.1 or Release 2.0. If it becomes necessary to fall back
from Release 2.1 or Release 2.0 and reinstall Release 1.8, note these important
considerations:
•
Check that SQL/MP metadata copied by migrate remains in its original locations
on the node. Among other things, this approach guarantees that, if you need to
reinstall Release 1.8, your original SQL/MP metadata is preserved intact.
•
If you modify or create new SQL/MP aliases, system defaults, ODBC metadata, or
SPJs in the Release 2.1 or Release 2.0 environment, there are no automated tools
for moving this new SQL/MX metadata to the SQL/MP metadata tables. To move
the new metadata, you will probably have to use manual methods like CREATE
SQLMP ALIAS, CREATE PROCEDURE, and INSERT INTO DEFAULTS
statements. For more information, see Appendix A, Falling Back From NonStop
SQL/MX Release 2.1 or Release 2.0.
Overview of Metadata Migration Using the migrate Utility
Use the migrate EXECUTE command to move metadata of a specified type. Use the
migrate ALL command to move all SQL/MP metadata. For a description of migrate
utility syntax, see the SQL/MX Reference Manual.
To use the migrate EXECUTE command with the SCRIPT option on metadata tables
of a specified type:
1. Set up the environment variables to specify the physical location for the SQL/MP
metadata table.
2. Use the migrate SHOW command to display the existing entries in the specified
SQL/MP metadata table.
3. Use the migrate PRELIMINARY_REPORT command to display any discrepancies
in the metadata files and direct this information to a file.
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 or to execute edited script.
7. Examine and resolve errors in the error log file.