ODBC Server Reference Manual

Managing Customized Catalogs
HP NonStop ODBC Server Reference Manual429151-002
7-34
USERCAT VALIDATE Statement
USERCAT VALIDATE has the following syntax:
catalog-name
specifies the name of the subvolume containing the NonStop SQL/MP catalog to
be validated. The catalog-name appears in Guardian format and can include the
node and volume. If you omit catalog-name, the current subvolume is used.
If the specified subvolume contains the system catalog, the mapping table that lists
all customized catalogs is validated.
Warning messages are generated if any mapping tables cannot be found.
output-filename
specifies the NonStop SQL/MP table name of the log table where command
response messages are written. The log table is an unaudited, entry-sequenced
table that NOSUTIL creates in the catalog where VALIDATE, REFRESH, or
INSTALL is being run. The log table also creates a mapping entry in the NonStop
ODBC master catalog. If a table that has the same name as output-filename
already exists, NOSUTIL appends the command response messages to the log
table.
Example
The following statement validates the NonStop SQL/MP catalog
\TEST.$VOL2.PERSNL:
usercat validate \test.$vol2.persnl
Effects of USERCAT VALIDATE
USERCAT VALIDATE reports on all object reference inconsistencies for any catalog
you specify. USERCAT VALIDATE verifies the following:
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.
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.
USERCAT VALIDATE [ catalog-name [ LOG output-filename ] ]