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

Table 17 Label Data Associated With SQL/MX Objects (continued)
ContentsLabel Field
The time and date when the last operation was performed against the SQL/MX catalog.Catalog operation
timestamp
The time and date when the file was last opened.Last open timestamp
Contains the creation version sequence number associated with the SQL/MX format object
stored in the file label by the DP2 for all disk files.
CRVSN
The number of primary extents allocated for the file.Primary extents
The number of secondary extents allocated for the file.Secondary extents
The maximum number of extents that can be allocated for the file.Maximum extents
The length of the blocks that compose the file.Block length
The number of data bytes in the file.EOF
The byte-length of the file records.Record length
The number of levels of indexing on the file.Number of index levels
The length of the keys used to access records in the file.Key length
The maximum byte-length of packed records.Maximum packed record
length
Flags that indicate whether the object is an SQL/MX format object, and whether the object
is a resource fork, audited, in the middle of a DDL operation, left in the crash-open state,
broken, offline, or SQLsecured.
Flags
SQL/MX version identifier.High-level SQL version
(HLSQLV)
Resource Fork Run-Time Metadata
Table 18 (page 256) on page 12-29 describes the run-time metadata that is stored in the resource
fork for SQL/MX format objects.
Table 18 Run-time metadata Stored in the Resource Fork
ContentsRun-time metadata
A three-part name of the form catalog.schema.object, where each part can be up
to 128 characters long.
ANSI name
Indicates the space the ANSI name belongs to. In NonStop SQL/MX, tables and indexes
have separate namespaces; indexes and tables in the same schema can have the same
ANSI namespace
ANSI names. The ANSI namespace is a two-letter literal that indicates the namespace the
ANSI name belongs to (for example, “TA” for table namespace, “IX” for index namespace,
and so on).
Indicates the location of system metadata tables and is of the form $volume.subvolume,
where subvolume is generally ZSD0.
System metadata location
Similar to SQL/MP format objects with respect to the information it stores, but the format
and possible data types are different.
Record descriptor
Similar to SQL/MP format objects with respect to the information it stores, but the format
and possible data types are different.
Key descriptor
Includes the object feature version and object schema version for the SQL/MX format object.Version information
For SQL/MX format objects that are partitioned, contains the list of all the partitions, along
with the partitioning key. Note that SQL/MX format objects can have multiple partitions
Partition array
on the same disk, which means that the partition array entries must contain the fully qualified
partition name, not just the disk name, as is the case for SQL/MP format objects.
256 Performing Recovery Operations