SQL/MP Installation and Management Guide

Moving a Database
HP NonStop SQL/MP Installation and Management Guide—523353-004
9-32
Renaming or Renumbering a Node
This example shows a DUP command in which the CATALOG specification identifies
individual objects. The objects residing on $VOL2.PERSNL are to be described in
several catalogs.
>> DUP $VOL1.PERSNL.*,
+> MAP NAMES ($VOL1.PERSNL.* TO $VOL2.PERSNL.*),
+> CATALOG ($VOL2.PERSNL FOR $VOL2.PERSNL.EMPLOYEE,
+> $VOL2.PERSNL FOR $VOL2.PERSNL.XEMPNAME,
+> $VOL2.SALES FOR $VOL2.PERSNL.ORDREP);
Renaming or Renumbering a Node
Choose your node name and number carefully to avoid the need to change them in the
future. The node name is expanded in the catalog entries, and the node number is
entered in the file labels throughout the database. SQL/MP relies on the file names and
node numbers of SQL objects. If you rename or renumber a node without changing the
file labels, SQL generates an error the next time one of the SQL objects on that node is
used or referenced.
A change to a node name or number in a distributed environment requires one of these
procedures:
•
Backing up, purging, and restoring these SQL objects:
°
All SQL noncatalog objects on the affected node
°
All SQL objects that have a partition on the affected node
°
All SQL objects that refer to an object on the affected node, such as dependent
objects (views, indexes, constraints)
•
Using the MODIFY DICTIONARY utility to change the node name or node number
or to register a user catalog in the local system catalog. Before using the MODIFY
DICTIONARY utility, see the Nomadic Disk Subsystem User’s Guide for a detailed
description of the process, including coordination with TMF operations. The
general steps are:
°
Backing up these SQL objects:
°
All SQL non-catalog objects on the affected node
°
All SQL objects that have a partition on the affected node
°
All SQL objects that refer to an object on the affected node, such as
dependent objects (views, indexes, constraints)
Note. To verify that the file labels of SQL objects contain the correct internal file names, you
must back up and purge all SQL objects from a node before the node is renumbered and
then restore the objects after the renumbering operation. Alternately, use the MODIFY
DICTIONARY utility, described next.