NonStop SQL/MP Reference Manual

NonStop SQL/MP Reference Manual—142115
M-9
Considerations—MODIFY CATALOG
°
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 commands.
°
User-defined SQL object files. For example, MODIFY CATALOG 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, then 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 the 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 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 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 node is in a consistent state, you can use the DISPLAY USE OF
command to locate dependent objects. After MODIFY commands are executed,
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 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 execute 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 does not mark SQL object programs as invalid in either
the catalog or in the object program file label.
°
MODIFY CATALOG 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