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-13
Steps for Migrating PROCS and PARAMS Metadata
to SQL/MX Release 2.x
The command displays this result:
The
PRELIMINARY REPORT command displays these types of discrepancies in
the SPJs to be migrated:
•
References in the PROCS table to catalogs or schemas that do not exist in
SQL/MX
•
References in the PROCS table to class or JAR files that do not physically
exist on the disk
PRELIMINARY_REPORT:
Checking for missing catalogs and schemas for MPALIAS Migration...
...
PRELIMINARY_REPORT:
Checking for missing Guardian files for MPALIAS Migration...
\POOH.$MXQA01.SQL.OPTABLE does not exist and is referenced.
...
PRELIMINARY_REPORT:
Checking for missing SQL/MP tables for ODBC Migration...
All necessary ODBC tables exist.
PRELIMINARY_REPORT:
Checking for missing catalogs and schemas for PROCS Migration...
PUBS.SUSAN: CATALOG AND SCHEMA DO NOT EXIST IN THE MX ENVIRONMENT
PRELIMINARY_REPORT:
Checking for missing OSS files for PROCS Migration...
/PUB/susan/PrintTest.class does not exist and is referenced. Check jar
files for class.
/PUB/susan/ErrorTesting.class does not exist and is referenced. Check jar
files for class.
/PUB/susan/ErrorTesting.class does not exist and is referenced. Check jar
files for class.
/PUB/susan/ErrorTesting.class does not exist and is referenced. Check jar
files for class.
/PUB/susan/ErrorTesting.class does not exist and is referenced. Check jar
files for class.
--------------------------------------------------------------------------
PRELIMINARY_REPORT: Summary of Preliminary Scan
Unique Catalogs and Schemas: 112 out of 142 need to be resolved.
SQLMP ALIAS Migration-Guardian Name Space Files: 472 out of 5839 files
missing.
ODBC Catalog Tables are available: 0 out of 5 tables missing.
PROCS Migration-OSS Name Space Files: 7 out of 443 files missing.
--------------------------------------------------------------------------
Note. When you run the PRELIMINARY REPORT command, the migrate utility might
report that these items do not exist on the SQL/MX Release 2.x system:
•
TANDEM_SYSTEM_NSK.SYSTEM_SQLJ_SCHEMA schema
•
Internal class file in mxlangman.jar
You can ignore those messages and continue the migration process. The
NONSTOP_SQLMX_NSK.SYSTEM_SQLJ_SCHEMA schema and internal class file should
already be part of SQL/MX Release 2.x if you installed it correctly. Do not create the
TANDEM_SYSTEM_NSK.SYSTEM_SQLJ_SCHEMA schema, which is an SQL/MX Release
1.8 schema, in an SQL/MX Release 2.x database.