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

REPLICATION_RULENODE_NAMECAT_UID
(for manual replication)
M\N312345678912345678
CAT_UID contains the 17-digit UID for each catalog.
• The SCHEMA_REPLICAS table on \N1 contains two rows for CAT1, one for each of its two
schemas. This includes these entries in the SCHEMA_UID and NODE_NAME columns:
NODE_NAMESCHEMA_UID
\N112345678912345678
\N123456789123456789
SCHEMA_UID contains the 17-digit UID for each schema.
System Schema Tables on Nodes \N2 and \N3
Nodes \N2 and \N3 each has an empty catalog reference for catalog CAT1. The system schema
tables on each of these nodes contain this information:
• The CATSYS table on \N2 and \N3 contains one row for the catalog CAT1, including these
entries in the CAT_NAME and REPLICATION_RULE columns:
REPLICATION_RULECAT_NAME
MCAT1
• The SCHEMATA table on \N2 and \N3 contains the same information about CAT1 in its
schemas that \N1 does.
• 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:
REPLICATION_RULENODE_NAMECAT_UID
A\N112345678912345678
M\Nn (where n is the local node)12345678912345678
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 20 (page 274) describes the statement and commands used to manage catalog references
in SQL/MX Release 3.x.
Managing a Network-Distributed SQL/MX Database 273