SQL/MX 2.x Reference Manual (H06.10+, J06.03+)

SQL/MX Utilities
HP NonStop SQL/MX Reference Manual—544517-008
5-105
Considerations for mximportddl
SQL/MX objects. The generated files are named as shown in the following
table:
n starts at 0 and increments by one. A new file is created every time when the
current file becomes full.
-SHOWDDLLOC oss-directory
places the files containing DDL information in the specified oss-directory. The
oss-directory must be a valid OSS directory.
Guidelines
•
Along with the -SHOWDDLLOC oss-directory option, the SHOWDDL ON
option needs to be enabled.
•
If the OSS directory already contains files with the same name as the files that
are being generated, the original files are overwritten.
-PREPAREMAP
generates the MAP file from the provided XML file. No object will be imported. The
generated MAP file can be used to map the parent object names and Guardian
locations of the SQL/MX objects.
Considerations for mximportddl
You must be the super ID or schema owner to run mximportddl.
You can edit the XML file manually using simple text editors. However, this method can
be error-prone and is not recommended.
As the schema owner information in the XML file can be updated, other users can
import the schema and its objects.
Remote catalogs must be registered manually before executing mximportddl. While
importing, mximportddl will not register catalogs on the remote system.
mximportddl supports the RI actions CASCADE/SET NULL/SET DEFAULT in
addition to NO ACTION and RESTRICT.
Supported by mximportddl
•
Tables and associated objects such as indexes and partitions
File Name Purpose Subordinate object of...
SHOWDDLn_RI_Constraints Referential integrity Table
SHOWDDLn_Stored_Procedur
es
Java stored
procedures
Schema
SHOWDDLn_Triggers Triggers Table
SHOWDDLn_Views Views Schema