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

where cat_name = 'SAMDBCAT'
)
)
for read uncommitted access;
GRANTABLE
---------
PRVTYPE
-------
GRANTEE_T
---------
GRANTEE_ID
-----------
GRANTOR_T
---------
GRANTOR_ID
----------
Y
Y
Refer
Update
Unknown
Unknown
65535
65535
System
System
-2
-2
Displaying Information About Sequence Generators
The SEQUENCE_GENERATORS metadata table is located in the schema
DEFINITION_SCHEMA_VERSION_version-number of each catalog. It stores information about
all the sequence generators in the catalogs.
Displaying all Sequence Generators
This example displays all the sequence generators in a catalog SGCAT:
>>select substr (o.object_name, 1, 10), s.sql_data_type,
>>s.cycle_option from sgcat.definition_schema_version_3200.objects o,
>>sgcat.definition_schema_version_3200.sequence_generators s
>>where o.object_uid = s.object_uid;
CYCLE_OPTION
------------------
SQL_DATA_TYPE
-----------
(EXPR)
--------
NSIGNED LARGEINTS1
YSIGNED NUMERICS2
For more information, see the SQL/MX Reference Manual.
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.
NOTE: HP recommends that you run the mxtool VERIFY command once a week on frequently
used objects for early problem detection and resolution.
For more information, see the SQL/MX Reference Manual.
Displaying Version Numbers
Topics in this subsection:
• “Displaying the NonStop SQL/MX Release Identifier” (page 148)
• “Displaying the Schema Version” (page 148)
• “Displaying the System Schema Version” (page 148)
Displaying Information About Sequence Generators 147