ODBC Server Reference Manual

Managing Customized Catalogs
HP NonStop ODBC Server Reference Manual—429151-002
7-33
USERCAT VALIDATE Statement
Example
The following statement validates the NonStop SQL/MP system catalog:
syscat validate
Effects of SYSCAT VALIDATE
SYSCAT VALIDATE reports all object reference inconsistencies for the system catalog.
SYSCAT VALIDATE verifies that:
•
Mapping tables and views exist.
•
The name of the database is registered in the NonStop ODBC Server system
catalog.
•
Tables, views, and indexes with mapping table entries actually exist as NonStop
SQL/MP objects and are the correct object type.
•
Entries in ZNSUS refer to valid Guardian usernames and user IDs
•
Mapping table entries that refer to NOS_UID and T_UID correspond to a user
registered in ZNSUS.
•
Stored procedures referred to in ZNUPCOL are found in ZNUPROC.The number of
input and input-output parameters in ZNUPROC equals the number of columns
defined in ZNUPCOL for input and input-output parameters.
•
All entries in SYSDATABASES correspond to NonStop ODBC Server customized
subvolumes and NonStop SQL/MP catalogs.
SYSCAT VALIDATE also produces a list of all exceptions detected.
USERCAT VALIDATE Statement
Use the USERCAT VALIDATE statement to report all referential inconsistencies within
the mapping tables in a user catalog.
Nonexistent objects are reported in your mapping tables if you do the following:
•
Drop mapped tables using NonStop SQL/MP or using the NonStop ODBC Server
in pass-through mode.
•
Drop a table without dropping dependent views and indexes. When you drop a
table that has dependent objects, the dependent objects are dropped from the
NonStop SQL/MP catalog, but they remain in the mapping tables. For more
information, see DROP TABLE on page 3-48, or in Section 4, Transact-SQL
Language.
Mapping tables will be missing if you accidentally purge them.
SYSCAT VALIDATE also reports any object owner name not found in the system users
(ZNSUS) mapping table.