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

Querying SQL/MX Metadata
HP NonStop SQL/MX Installation and Management Guide—523723-004
8-62
Displaying Object Integrity and Consistency
Displaying Object Integrity and Consistency
The mxtool VERIFY command detects and reports inconsistencies between the
information contained in the metadata, the resource forks, and the file labels. It does
not verify data integrity. This command is often used together with the mxtool INFO
command, which displays various aspects of a database.
An object has definitional integrity if it is consistently described in the metadata, the
resource forks, and the file labels, and if the descriptions of all related objects are valid.
A database can become inconsistent through database changes that are not applied
consistently throughout related objects. SQL can prevent many of the operations that
cause inconsistency, but it does not always detect all operational errors. For example,
when you drop a table, SQL attempts to drop all dependencies. However, a user might
restore objects that might not be consistent with the related objects. System
operational problems or system failures can also cause inconsistencies in the data
dictionary.
For detailed information and examples of the mxtool VERIFY command, see the
SQL/MX Reference Manual.
Displaying Version Numbers
Topics in this subsection:
•
Displaying the SQL/MX Release Details on page 8-62
•
Displaying the Schema Version on page 8-62
•
Displaying the System Schema Version on page 8-63
•
Displaying the Object Schema Version (OSV) on page 8-63
•
Displaying the Object Feature Version (OFV) on page 8-63
Displaying the SQL/MX Release Details
To determine which release of the SQL/MX software is running on a specified node,
see the banner generated by mxci. For both NonStop SQL/MX Release 2.1 and
Release 2.0 systems, mxci displays 2.0.
Displaying the Schema Version
This example displays the version number of a specified schema:
>> select s.schema_version
from nonstop_sqlmx_node.system_schema.schemata s,
nonstop_sqlmx_node.system_schema.catsys c
where c.cat_name = 'catalog-name'
Note. HP recommends that you run the mxtool VERIFY command once a week on
frequently used objects for early problem detection and resolution.