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-11
Steps for Migrating PROCS and PARAMS Metadata
to SQL/MX Release 2.x
4. Migrate ODBC entries from SQL/MP metadata to SQL/MX metadata by using the
EXECUTE command of the migrate utility.
•
To migrate all entries from the ODBC/MX metadata tables, enter:
/usr/tandem/sqlmx/bin: migrate EXECUTE ODBC
ERROR_LOG odbc_errors.out CLEAR
•
To migrate only ODBC entries in the script file, enter:
/usr/tandem/sqlmx/bin: migrate EXECUTE SCRIPT
odbc_script.out
ERROR_LOG odbc_errors.out CLEAR
If you do not specify the name and OSS location of the error log file, the default is
error_log.out in the current directory. If you specify an existing error log file,
use the CLEAR option to direct the
migrate utility to clear the contents of the file
before adding information about migration errors. If the error log file already exists
and you omit the CLEAR option, the
migrate utility uses error_log.out.
5. Examine and resolve errors in the error log file. The
migrate EXECUTE command
captures information about the metadata entries that fail to migrate to SQL/MX
Release 2.x and logs the information in the error log file. Fix the errors in a script
file and run the
migrate EXECUTE SCRIPT command to migrate previously failed
metadata. See Steps 3 and 4.
Steps for Migrating PROCS and PARAMS
Metadata to SQL/MX Release 2.x
To use SPJs from SQL/MX Release 1.8 in SQL/MX Release 2.x, you must migrate the
metadata of the SPJs. Use the
migrate utility to copy metadata from the PROCS
table in the SQL/MP environment to the ROUTINES and TEXT tables in the SQL/MX
environment and from the PARAMS table in the SQL/MP environment to the COLS
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 PROCS and
PARAMS tables reside on the same node as SQL/MX Release 2.x:
Note. Because there are no discrepancies to report for the NonStop ODBC/MX metadata
tables, it is not necessary to use the PRELIMINARY_REPORT command to display
discrepancies. Use the SHOW SCRIPT command to generate a script file for editing purposes.
Note. Before migrating the metadata of SPJs, 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.