SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

Table 20 Statements and Commands for Managing Catalog References
DescriptionCommand
DDL statement that creates a new catalog at the specified location on the local node.CREATE CATALOG
MXCI command that registers a catalog on a remote node. The remote node then has an
empty catalog reference to the catalog.
REGISTER CATALOG
MXCI command that unregisters an empty catalog reference from a remote node.UNREGISTER
CATALOG
For more information, see the SQL/MX Reference Manual.
Catalog Creation and Registration Examples
For catalog creation and registration examples, see “Creating, Registering, and Unregistering
Catalog References” (page 278).
Managing Network Security
Managing a network-distributed SQL/MX database imposes few additional security requirements
than those of managing a locally distributed database.
Users of a distributed node must have remote passwords for remote network access. The access
privileges assigned by GRANT to users for SQL/MX objects on the local node also apply to those
users when the objects are located on a remote node or are accessed from a remote node to which
a user has remote access authorization.
Maintaining Local Autonomy in a Network for SQL/MX Release 3.x
In the context of a network distributed database, local autonomy ensures that a user can access
local data regardless of the availability of remote dependent objects. For SQL/MX Release 3.x,
these restrictions apply:
• Dynamic DDL and DML operations must have access to object metadata. If the node on which
the object metadata is located becomes unavailable, other network nodes cannot perform
dynamically compiled DDL or DML operations on that object data to any node.
• To use late name resolution of ANSI names or automatic recompilation with static DML
operations, the object metadata must also be accessible. However, static DML statements that
do not use ANSI names, late name resolution of ANSI names, or automatic recompilation can
execute locally if the node on which the object metadata is stored is not available.
• For objects that are partitioned across network nodes, you cannot perform DDL operations on
any partitions in the network—even those on available nodes—if one of the partitioned nodes
becomes unavailable. For example, if a table is partitioned across two nodes and one node
goes down, the surviving node cannot drop the partitioned table. The same is true of DML
operations that use late name resolution of ANSI names or automatic recompilation.
These SQL/MX operations require access to object metadata. Therefore, if the node containing
the object metadata is unavailable, you cannot perform these SQL/MX operations on the associated
object data from any network node:
• DDL and utility operations (for example, CREATE TABLE, IMPORT, UPDATE STATISTICS)
• Dynamic compilation of DML queries (for example, SELECT, including queries entered from
MXCI and NonStop ODBC/MX)
• Static compilation of modules
• Run-time ANSI name resolution of DML queries (for example, queries that use host variables
and prototyping to specify the database object names at runtime)
• Run-time automatic recompilation of DML queries
274 Managing an SQL/MX Distributed Database