SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Performing Recovery Operations
HP NonStop SQL/MX Installation and Management Guide—523723-004
12-29
Identifying Problem Data and Objects
Using SHOWLABEL to Retrieve Run-Time Metadata
You can also use the SHOWLABEL command to retrieve run-time metadata from both
the labels and the resource fork of a Guardian file. For command syntax and example
outputs, see the SQL/MX Reference Manual.
SHOWLABEL displays this information:
•
The ANSI file name
•
The ANSI namespace, including table namespace (which includes views and
SPJs), index namespace, and trigger namespace
•
The object schema version
Using VERIFY to Check Data Consistency
Infrequently, information between labels, resource forks, and metadata becomes
inconsistent. The VERIFY operation detects and reports these inconsistencies. For
command syntax and example outputs, see the SQL/MX Reference Manual.
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.