SQL/MP Installation and Management Guide

Querying SQL/MP Catalogs
HP NonStop SQL/MP Installation and Management Guide—523353-004
6-12
Determining Object Integrity and Consistency
•
The name of a program stored in an OSS file is displayed as its Guardian file name
equivalent and then in its path name format. If there is more than one path name
linked to the program, only one path name is displayed (the first path name
available to the current user).
•
Several informational items are not displayed because they do not apply to OSS
files. For example, the EXTENTS option displays a message that EXTENTS
information does not apply to an OSS file.
As an alternative, run FUP or OSS utilities to obtain information about an OSS file.
Determining Object Integrity and Consistency
Two tools are available to verify the definitional integrity of an object or to check the
consistency of an object’s internal blocks:
•
The SQLCI VERIFY utility checks the definitional integrity of an object.
•
The Guardian FILCHECK utility reports on the internal, physical data structure of
objects and checks that the structure is consistent.
Using VERIFY to Check Definitional Integrity
The VERIFY utility determines the definitional integrity of an object. The utility does not
verify data integrity. An object has definitional integrity if it is consistently described in
all file labels and catalog tables and if the descriptions of all related objects are valid.
The database can become inconsistent through database changes that are not applied
consistently throughout the related objects. SQL can prevent many of the operations
that can cause inconsistency, but it does not always detect all the operational errors.
For instance, when you drop a table, SQL attempts to drop all dependencies; however,
a user could restore objects that might not be consistent with the related objects.
System operational problems or system failures could also cause inconsistencies in
the data dictionary.
You can use VERIFY to check catalogs, tables, views, indexes, collations, and
programs. VERIFY checks each object for dependent relations or underlying table
consistency, as required by the object.
For SQL programs stored in OSS files, VERIFY checks for consistency between the
label and the catalog information for [IN]VALID, PFV, and PCV.
For information on invalid programs, see Determining Validity of a Program on
page 10-4.
The VERIFY utility uses a qualified file set list to assist you in identifying a specific
object or group of objects. You can verify programs and have the list of invalid
programs written to an EDIT file. This example verifies all objects that are in the