SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual—523352-013
V-4
Considerations—VERIFY
view columns and the SELECT clause of a protection view are the same in the
catalog and in the file label.
For a shorthand view, VERIFY checks descriptions of the view. However, VERIFY
does not check whether data types of view columns are the same in the catalog
and in the file label.
For an index, VERIFY checks descriptions of the index and its base table, views of
the base table, and partitions. VERIFY also checks the consistency of base table
and partition entries in related file labels.
For an SQL program, VERIFY checks whether the program is valid or invalid and
also checks the consistency of the PCV and PFV values in related file labels. For
an SQL program in a Guardian file, VERIFY also checks descriptions of the
program.
For a catalog, VERIFY checks descriptions of each catalog table and each
SQL-supplied index or protection view on a catalog table.
For partitioned objects, VERIFY makes the checks previously described for each
partition of the object. However, VERIFY does not check whether first key values
for partitions are the same in the catalog and in the file label.
VERIFY does not check whether a file label is internally consistent with itself.

If VERIFY locates an invalid object, you might want to change the VALIDDEF flag
in the appropriate catalog table to prevent further use of the object until the
problem is corrected. (For example, if a view is invalid, change the value of the
VALIDDEF column of the VIEWS table to N.) A user with the super ID can change
values in a catalog table by using the UPDATE command with a licensed version of
SQLCI2. For more information about using a licensed SQLCI2 process, see the
SQL/MP Installation and Management Guide.

A program can be invalid for a variety of reasons. In some cases, the appropriate
action is to recompile the program. In other cases (especially if the program uses
execution-time name resolution), you might want to continue using the invalid
program. For more information about changes that can cause program invalidation,
see Program Invalidation
on page P-28.
If VERIFY returns SQL error -9853 (a column in the catalog table is corrupted) for a
program file, SQL-compiling the program again might correct the problem.

Avoid using VERIFY within user-defined transactions, because it reduces
concurrency for other operations. If a user-defined transaction is not in progress
when you execute VERIFY, SQL automatically starts a transaction before verifying
each object or program and ends the transaction when the verification of that
object or program is complete.
You can use the Break key to interrupt a VERIFY operation. If you roll back the
transaction and want to restart the operation, you must issue the VERIFY
command again.