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-12
Steps for Migrating ODBC Metadata From Release
1.8 to Release 2.1 or Release 2.0
3. Migrate the DEFAULTS entries from the SQL/MP metadata to the SQL/MX
metadata by using the EXECUTE command of the migrate utility:
•
To migrate all entries from the DEFAULTS table, enter:
/usr/tandem/sqlmx/bin: migrate EXECUTE DEFAULTS
ERROR_LOG defaults_errors.out CLEAR
•
To migrate only DEFAULTS entries in the script file, enter:
/usr/tandem/sqlmx/bin: migrate EXECUTE SCRIPT
defaults_script.out
ERROR_LOG defaults_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.
4. Examine and resolve errors in the error log file. The migrate EXECUTE command
captures information about the metadata entries that fail to migrate to Release 2.1
or Release 2.0 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 2 and 3.
Steps for Migrating ODBC Metadata From Release 1.8 to Release
2.1 or Release 2.0
These steps assume that you have upgraded a Release 1.8 environment to Release
2.1 or Release 2.0 and that the ODBC tables (ZOAS2DS, ZODS, ZOENV,
ZONAME2ID, and ZORES) reside in the SQL/MP environment on the same node as
Release 2.1 or Release 2.0:
1. 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 SQL/MP
ODBC tables reside.
Note. Because there are no discrepancies to report for the DEFAULTS table, 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. The migrate utility runs only on the OSS command line and is case-sensitive.