SQL/MX 3.2 Management Manual (H06.25+, J06.14+)

VERIFY performs these actions:
• Checks for inconsistencies between an SQL/MX table and its structural representation in the
resource fork.
This feature compares information saved in the resource fork with similar information stored
in metadata and returns inconsistencies. This information is compared:
◦ ANSI name. The ANSI name stored in the resource fork must match that stored in metadata.
◦ ANSI namespace. The ANSI namespace stored in the resource fork must match that stored
in metadata.
◦ Partition map. The number of partitions defined in the PARTITIONS table must match the
number of partitions in the partition map array in the resource fork.
◦ Version information. The object schema, object feature, and resource fork versions must
match.
◦ For dependent indexes, similar checks are made for the indexes resource fork and
metadata.
◦ Constraint information associated with a table must match that stored in the resource fork.
Constraint information stored in the resource fork is used during similarity checking to
determine 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.
• Checks for inconsistencies between an SQL/MX table, view, or an SPJ and its structural
representation in corresponding DP2 file labels.
This VERIFY feature compares information saved in the DP2 file label with similar information
stored in metadata and returns inconsistencies. This information is compared for each Guardian
file associated with the object:
◦ Redefinition time
◦ Extent sizes (primary extent size, secondary extent size, maxextents)
◦ Audit flag
◦ Corrupt flag
For dependent indexes and for each table that contains an index, VERIFY ensures that the
index map array exists and contains the correct number of indexes.
• Checks that dependent, partitionable objects exist and are defined correctly.
For each partition of a table and any dependent indexes, VERIFY checks that:
◦ The encoded key values are the same.
◦ The physical locations are the same.
◦ The partition map in the resource fork contains all partitions defined for the table (except
offline partitions).
◦ The partition map stored in the index map array of a table is correct.
Security Considerations
• VERIFY does not check privilege information.
• You must be logged on using the super ID, be owner of the schema where the object being
verified resides, or have SELECT privilege on the object being verified.
Repairing Damaged SQL/MX Metadata and Objects 255