NonStop SQL/MP Reference Manual

NonStop SQL/MP Reference Manual—142115
M-18
Examples—MODIFY LABEL
It is the responsibility of the user to know how the database is distributed and
partitioned. Document the MODIFY commands that need to be executed—and
what nodes they need to be executed on—before they are needed. Prepare
scripts that execute the necessary MODIFY commands. When you add a new
dependent object to the database, update the scripts.
While the system is in a consistent state, you can use the DISPLAY USE OF
command to locate dependent objects. After MODIFY commands have been
executed, you can use the VERIFY utility to verify that the database is in a
consistent state.
While the system is in a consistent state, issue a SELECT from the PARTNS
partitions table to locate partitions. Prepare scripts that execute the necessary
MODIFY commands. After MODIFY commands are executed, use the
VERIFY utility to verify that the database is in a consistent state.
°
MODIFY LABEL does not mark SQL object programs as invalid in either the
catalog or in the object program file label.
°
MODIFY LABEL does not change the redefinition timestamp in either the
catalog or the file label.
•
DEFINE names can be used in programs to specify the 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 executed, the DEFINEs must be
changed to reflect the new location of the objects and object programs. This
instruction is true regardless of how the database was moved or whether the
MODIFY DICTIONARY utility was used to modify the node names and numbers.
The MODIFY DICTIONARY utility does not modify the 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.
•
A catalog and the objects registered in it must be on the same node. However, it is
possible for an object to be on a different disk than its catalog. 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 LABEL command returns a nonfatal versioning error if an SQL
object is newer than the version of MODIFY DICTIONARY accessing it, if the
PCV of an SQL program is newer than the version of MODIFY that is accessing it,
or if the object or program has a version newer than the version of NonStop
SQL/MP system software on the node where the object or program resides.
Examples—MODIFY LABEL
The first group of examples show the REPLACE clause.