SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual—523352-013
M-10
Considerations—MODIFY CATALOG with
REPLACE NODENAME
be run on, before they are used. Prepare scripts that run the necessary
MODIFY commands. When you add a new dependent object to the database,
update the scripts.
While the node is in a consistent state, you can use the DISPLAY USE OF
command to locate dependent objects. After MODIFY commands are run, use
the VERIFY utility to verify that the database is in a consistent state.

Partitioned objects. For a partitioned SQL object, each volume that contains a
partition of the object must be specified separately. MODIFY CATALOG with
REPLACE NODENAME does not automatically modify information about all
partitions of a partitioned object.
It is the responsibility of the user to know how the database is partitioned.
While the node is in a consistent state, issue a SELECT from the PARTNS
partitions table to locate other partitions. Prepare scripts that run the necessary
MODIFY commands. After running the MODIFY commands, use the VERIFY
utility to verify that the database is in a consistent state.

MODIFY CATALOG with REPLACE NODENAME does not mark SQL object
programs as invalid in either the catalog or in the object program file label.

MODIFY CATALOG with REPLACE NODENAME does not change the
redefinition timestamp in either the catalog or the file label.

You can use DEFINE names in programs to specify names of catalogs, tables,
views, indexes, partitions, and other programs. The current DEFINE set at the
time the program is SQL compiled is saved in the object program file. If objects
or object programs specified by the DEFINEs are moved between the time that
the program is SQL compiled and the time that the program is run, the
DEFINEs must be changed to reflect the new location of the objects and object
programs. This guideline is true regardless of how the database was moved
and regardless of whether the MODIFY DICTIONARY utility was used to
modify the node names and numbers.
The MODIFY DICTIONARY utility does not modify node names in the DEFINE
set stored in the object program file. After the DEFINEs are changed by the
user, if automatic recompilation is enabled, the programs are automatically
recompiled using the new DEFINEs.

The MODIFY DICTIONARY utility is not intended to correct the situation where a
disk containing objects is moved to a new node, but the disk containing the
associated catalog is not moved to the new node.

The MODIFY CATALOG with REPLACE NODENAME command returns a nonfatal
versioning error if an SQL catalog has a version newer than the version of
MODIFY that is accessing it, or if the catalog has a version newer than the version
of SQL/MP system software on the node where the catalog resides.