SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual—523352-013
M-9
Considerations—MODIFY CATALOG with
REPLACE NODENAME
volume name in file label), and MODIFY REGISTER Command (to register user-
defined catalogs in the local system catalog).

Multiple MODIFY commands (including LABEL, CATALOG, and REGISTER
commands) can be run concurrently on the same node as long as each command
is processing a different set of files or catalogs. For example, if the node number is
changed on a node that has an SQL database spread out over five volumes, five
MODIFY LABEL commands can be started concurrently, each specifying a
different volume to be modified. Note that in such a case, because the node name
did not change, it would not be necessary to run any MODIFY CATALOG with
REPLACE NODENAME commands.

Before requesting a MODIFY CATALOG with REPLACE NODENAME operation for
a catalog, do a MODIFY LABEL with REPLACE NODENUMBER operation on all
catalog tables in the catalog.

MODIFY CATALOG with REPLACE NODENAME locks one catalog table at a time.
The file labels of the catalog tables are not locked. Do not request DDL or update
operations until the node names are modified, including operations on partitions
and on dependent objects on remote nodes.

The MODIFY DICTIONARY utility does not handle:

Remote nodes. If you specify a remote file name or catalog name, the MODIFY
command reports a nonfatal error. Therefore, each node with dependent
objects or partitioned objects must have a version of NonStop SQL/MP that
supports MODIFY CATALOG with REPLACE NODENAME commands.

User-defined SQL object files. For example, MODIFY CATALOG with
REPLACE NODENAME does not modify a node name stored in a column of a
user-defined table.

Names stored in SQL object program files. SQL object programs can refer to
an SQL object by using either a DEFINE or the Guardian name of the object. If
DEFINEs are used, both the DEFINE name and the associated Guardian
name of the SQL object are stored in the object program file—not in the file
label. If Guardian names are used, the Guardian names are stored in the
object program file in internal network form.

Node names in Enscribe files. If a disk containing an alternate key file or a
partition file is moved to a different node, the FUP ALTER command can be
used to change the Enscribe file label that references the file that moved. Note
that changes must be made to the Enscribe file labels that point to the disk that
moved, not to the alternate key file label or partition file label that resides on
the disk that moved.

Dependent objects. The MODIFY CATALOG with REPLACE NODENAME
command does not modify information about dependent objects that reside in
other catalogs unless the other catalogs are specified.
It is the responsibility of the user to know how the database is distributed.
Document the MODIFY commands that need to be run, the nodes they need to