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

Table 18 Run-time metadata Stored in the Resource Fork (continued)
ContentsRun-time metadata
Contains the list of all indexes on the SQL/MX format object (if the object is a table), along
with index key information and a list of partitions associated with each index.
Index map array
Contains entries for droppable check constraints. This information is needed for
similarity-checking to determine whether plans need to be recompiled because of a new
or deleted check constraint.
Constraint information
Indicates whether or not a trigger is enabled.Trigger information
The low-key and high-key information for the partition of the SQL/MX format object used
by DP2 to do key-range checking, as is the case for SQL/MP.
Key range information
Contains the logical name information that uniquely identifies the partition of the SQL/MX
format object.
Logical partition name
information
Contains the ANSI name associated with the parent SQL/MX format object. This information
is useful for ANSI indexes.
Parent object ANSI name
The unique IDs associated with the SQL/MX catalog and schema in which the SQL/MX
format object is registered, as well as the unique ID of the SQL/MX format object itself.
ANSI unique identifiers
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 more information, 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 more information, see the SQL/MX
Reference Manual.
Repairing Damaged SQL/MX Metadata and Objects 257