Manualshelf

SQL/MP Installation and Management Guide

ManualsBrandsHP ManualsServerHP NonStop G-Series
361362363364365366367368369370
Managing a Distributed Database
HP NonStop SQL/MP Installation and Management Guide—523353-004
12-3
Naming Nodes
Naming Nodes
An SQL/MP system requires a node name. An SQL/MP system in a network requires a
node number in addition to a node name.
After an SQL/MP database is created using a node name and node number, you
should minimize changes to the name and number. The node name is expanded in the
catalog entries, and the node number is entered in the file labels throughout the
database. Choose your node name and number carefully so that you will not need to
change them in the future.
Using DEFINEs for Network Object Names
When you work with distributed objects, always fully qualify each reference, either in
each statement or by using DEFINEs.
Use DEFINEs for a network distributed database in the same way you would for a local
system. For a network distributed system, however, you should include the node name
in the DEFINE name to avoid any confusion about the applicable node.
A possible format for DEFINE names that include the node name follows:
=node-name_define-name
These DEFINE names are examples of distributed names:
=REMOTE1_EMPLOYEE, CLASS MAP, FILE
\REMOTE1.$VOL1.PERSNL.EMPLOYEE
=LOCAL_XEMP, CLASS MAP, FILE \LOCAL.$VOL3.PERSNL.EMPLOYEE
Always qualify the =_DEFAULTS DEFINE with the fully qualified name, including the
node name. Likewise, you should always fully qualify names in VOLUME and
CATALOG commands.
When using the SYSTEM command with SQLCI, the node (system) you specify is
stored in the volume.subvolume string. Then, when you specify Guardian names
without fully qualifying them, these names are expanded with the fully qualified volume
string that includes the node you specified.
The CATALOG string also stores a fully qualified catalog name, such as
\SYS1.$VOL1.SALES. The CATALOG command qualifies a partially specified catalog
name by using the current node and does not automatically expand the name by
using the node name stored in the SYSTEM volume.subvolume string.