SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual—523352-013
V-3
Considerations—VERIFY
You can use edit-file with the TACL OBEY command to recompile the invalid
SQL programs in the Guardian files. (SQL does not generate commands to
recompile SQL programs in OSS files.)
CLEAR clears edit-file before writing SQLCOMP commands. If you omit
CLEAR, SQL appends commands to the existing text.
If SMF is installed on your node, edit-file must be either a logical or direct file.
[ REPAIR ]
directs VERIFY to re-create any missing SQL object using information available in
the catalog. The newly created object does not contain any data. The VERIFY
command with this option creates the physical object and checks the object for
definitional integrity. This option provides support for tables, partitions, views, and
indexes.
Considerations—VERIFY

VERIFY requires read authority for the objects being verified and for related
objects and catalogs.
VERIFY requests REPEATABLE access to object definitions in catalogs to prevent
DDL operations on the object during the VERIFY operation. If VERIFY cannot
attain REPEATABLE access, it issues a warning message and continues using
BROWSE access.
VERIFY also requests a SHARED lock on the file label of the object (including all
partitions of partition objects). If VERIFY cannot obtain the lock, it issues a warning
message and continues without the lock.

VERIFY checks for definitional integrity, but not for data integrity. An object or
program has definitional integrity if its description in the file label is consistent with
its definition in the catalog, and the descriptions of related objects in related disk
file labels are valid. Specific checks depend on the type of item being checked.
For all objects and SQL programs in Guardian files, VERIFY checks that the
version is the same in the file label and in the catalog. VERIFY also checks related
catalogs for relationships with other objects as described in the local USAGES
table.
For a table, VERIFY checks descriptions of the table and its columns, primary key
columns, indexes and index key columns, partitions, and protection views. VERIFY
also checks the consistency of index and partition entries in related file labels.
However, VERIFY does not check whether the text of a constraint associated with
a table is the same in the catalog and in the file label.
For a collation, VERIFY checks descriptions of the collation.
For a protection view, VERIFY checks descriptions of the protection view and its
base table and columns. VERIFY also checks the consistency of base table entries
in related file labels. However, VERIFY does not check whether the data types of