SQL/MX 3.2.1 Reference Manual (H06.26+, J06.15+)

SQL/MX Utilities
HP NonStop SQL/MX Release 3.2.1 Reference Manual—691117-005
5-81
Considerations for VERIFY
•
Number of indexes
•
Partition name
•
For dependent indexes, similar checks are made for inconsistencies, including:
°
ANSI name
°
ANSI namespace
°
Partition map
°
Version information
•
Constraint information.
Constraint information stored in the label is used during similarity checking to see if
the current plan can be executed or needs to be recompiled. The number of
constraints defined must be the same. In addition, the constraint text and disabled
attribute must match. Only droppable check constraint information is verified.
•
Redefinition time
•
Extent sizes (primary extent size, secondary extent size, maximum number of
extents)
•
Audit flag
•
Corrupt flag
If a table has offline partitions or unpopulated indexes defined in metadata, they are
noted in the output. If a table has both offline partitions and unpopulated indexes
defined in metadata, they will be ignored.
When the -oo option is used, VERIFY searches the set of Guardian files that match
the specified file-name-template. For each matching file, VERIFY checks if the
corresponding SQL/MX metadata exists. If not, that Guardian file is considered
orphaned, and its name is written to the specified output file.
After VERIFY has completed the search for orphaned Guardian files, the resulting
output file can be used as input to CLEANUP.
Security Considerations
•
VERIFY does not check privilege information.
•
VERIFY obtains read-only locks on metadata while verifying an object. Other
operations that read metadata can run concurrently. Operations that change
metadata or labels such as DDL, partition management, PURGEDATA, and
UPDATE STATISTICS statements cannot run concurrently.
•
To verify some objects NonStop SQL/MX might need to access remote systems.
The remote system must be available and you must have privileges to view
information on it.
•
If VERIFY tries to access objects that have a schema version that is greater than
the SQL/MX software version (MXV) of the local node, you receive a versioning
error.