SQL/MX 2.x Reference Manual (H06.04+)

Metadata Tables
HP NonStop SQL/MX Reference Manual—540440-003
10-2
Migrating SQL/MP Metadata
without the surrounding double quotes, and with two consecutive double quotes
collapsed into one double quote.
•
Unless otherwise stated, CHAR(n) in the data type field without a character set
qualifier is associated with the ISO88591 character set. All character types are
searched or sorted with the DEFAULT (binary) collation with the PAD SPACE
characteristic.
For SQL/MX Release 2.0, these tables are visible but are not supported and are
reserved for future use:
•
DDL_PARTITION_LOCKS
•
MODULES
•
MVGROUPS
•
MVS
•
MVS_COLS
•
MVS_JOIN_COLS
•
MVS_TABLE_INFO
•
MVS_USED
•
MVS_TABLE_INFO_UMD
•
MVS_USED_UMD
Migrating SQL/MP Metadata
The SQL/MP metadata tables used by SQL/MX Release 1.8 cannot be used in an
SQL/MX Release 2.x database. If you migrate from SQL/MX Release 1.8 to SQL/MX
Release 2.x, use the migrate utility to copy the metadata from these SQL/MP user
metadata tables to these SQL/MX Release 2.x system metadata tables:
•
SQL/MP MPALIAS table metadata is copied to the MP_PARTITIONS and
OBJECTS tables.
•
SQL/MP DEFAULTS table metadata is copied to the SYSTEM_DEFAULTS table.
•
ODBC metadata in the ZONAM2ID, ZOAS2DS, ZODS, ZOENV, and ZORES
tables is copied to the NAME2ID, ASSOC2DS, DATASOURCES,
ENVIRONMENTVALUES, and RESOURCEPOLICIES tables respectively.
•
Stored procedures in Java (SPJ) metadata in the PROCS table is copied to the
OBJECTS, ROUTINES, and TEXT tables. SPJ metadata in the PARAMS table is
copied to the COLS table.
For more information, see migrate Utility on page 5-42. For detailed instructions on
how to use the migrate utility to copy SQL/MP metadata from SQL/MX Release 1.8
to SQL/MX Release 2.x, see the SQL/MX Database and Application Migration Guide.