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-15
Steps for Migrating PROCS and PARAMS Metadata
to SQL/MX Release 2.x
9. Migrate the SPJ entries from the SQL/MP metadata to the SQL/MX metadata by
using the
EXECUTE command of the migrate utility:
•
To migrate all the SPJs directly from the PROCS table, enter:
/usr/tandem/sqlmx/bin: migrate EXECUTE PROCS
ERROR_LOG spj_errors.out CLEAR
•
To migrate only the SPJs in the script file, enter:
/usr/tandem/sqlmx/bin: migrate EXECUTE SCRIPT
spj_script.out ERROR_LOG spj_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.
10. 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 this information in the
error log file:
Fix the errors in a script file and run the
migrate EXECUTE SCRIPT command to
migrate the previously failed metadata. See Steps 6
, 7, and 9.
11. Secure the migrated SPJs by issuing GRANT EXECUTE or GRANT statements.
To grant privileges for invoking SPJs, see the
SQL/MX Guide to Stored Procedures
in Java.
Note. You can also execute the script file as an OBEY command file. For more
information about the OBEY command, see the SQL/MX Reference Manual.
== Error occurred: 2
CREATE PROCEDURE PUBS.SUSAN.STARS2( IN INT SIGNED ) external
name 'ErrorTesting.starsWithException2(int)' external path '/PUB/susan'
language JAVA parameter style JAVA contains SQL not deterministic
isolate
==
**************************************************************************
Note. Security settings or privileges that you established for SPJs in SQL/MX Release 1.8
by using surrogate files are not migrated to SQL/MX Release 2.x.