SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Managing an SQL/MX Distributed Database
HP NonStop SQL/MX Installation and Management Guide—523723-004
13-11
Managing Network Security
•
The CAT_REFERENCES table on \N2 and \N3 contains two rows for the catalog
CAT1, one for \N1 and another for the local node. The table includes these entries
in the CAT_UID, NODE_NAME, and REPLICATION_RULE columns:
During ANSI name lookup, these entries provide location information to nodes \N2
and \N3 for the object metadata for CAT1.
•
The SCHEMA_REPLICAS table on \N2 and \N3 contains no information about
CAT1 or its schemas.
System Schema Tables on Node \N4
The node \N4 has no catalog reference for the catalog CAT1 created on \N1. As a
result, the system schema tables on \N4 contain no information about it.
Commands for Managing Catalog References
Table 13-2 describes the statement and commands used to manage catalog
references in Release 2.1 or Release 2.0.
For more information about the DDL statement and MXCI commands, see the SQL/MX
Reference Manual.
Catalog Creation and Registration Examples
For catalog creation and registration examples, see Creating, Registering, and
Unregistering Catalog References on page 13-19.
Managing Network Security
Managing a network-distributed SQL/MX database imposes few additional security
requirements than those of managing a locally distributed database.
CAT_UID NODE_NAME REPLICATION_RULE
12345678912345678 \N1 A
12345678912345678 \Nn (where
n is the
local node)
M
Table 13-2. Statements and Commands for Managing Catalog References
Command Description
CREATE
CATALOG
DDL statement that creates a new catalog at the specified location on the
local node.
REGISTER
CATALOG
MXCI command that registers a catalog on a remote node. The remote
node then has an empty catalog reference to the catalog.
UNREGISTER
CATALOG
MXCI command that unregisters an empty catalog reference from a
remote node.