ODBC Server Reference Manual

Architecture Overview
HP NonStop ODBC Server Reference Manual—429151-002
2-38
NOSUTIL
Catalog Integrity
The NonStop SQL/MP tables that make up the NonStop ODBC Server catalogs include
certain integrity constraints, as follows:
•
For example, the NonStop ODBC Server system catalog has a table, ZNSDB, that
lists all customized NonStop SQL/MP catalogs supported for a given NonStop
ODBC system catalog (that is, all NonStop ODBC Server user catalogs), and only
those catalogs, on a NonStop node.
•
Another example: if alias username “A” is associated with logical username “U” (in
table ZNSALT), then “U” must have an entry in the username table (ZNSUS).
•
Finally, the NonStop ODBC Server catalogs have referential associations to the
NonStop SQL/MP objects they describe.
Administrators and users must understand how the NonStop ODBC Server handles
catalog integrity. The NonStop ODBC Server does not provide fully active support of
NonStop ODBC Server catalog integrity for two reasons:
•
Changes are managed manually
The NonStop ODBC Server is not notified by NonStop SQL/MP when some DDL
operation is performed on an object in the NonStop SQL/MP catalog associated
with a NonStop ODBC Server catalog. Therefore, the NonStop ODBC Server
administrator must reestablish referential integrity with specific NonStop ODBC
utility commands. Two utility functions are provided to do this.
One function is VALIDATE, which causes NOSUTIL to scan a designated NonStop
ODBC Server catalog and produce a report on integrity violations (such as a
NonStop SQL/MP table that is in the NonStop SQL/MP catalog, but that is not in
the NonStop ODBC Server catalog).
The second function is REFRESH, which causes NOSUTIL to alter the catalog to
fix any violations. REFRESH alters only the NonStop ODBC Server catalog; it does
not drop a NonStop SQL/MP table that is not in the NonStop ODBC Server catalog.
•
Better usability
When an administrator or user is making changes to a NonStop ODBC Server
catalog, such as defining a new alias name or profile, NOSUTIL does not check all
the integrity constraints. This allows catalog changes to be made in any order.
When a NonStop ODBC server is running, however, integrity in the NonStop ODBC
Server catalog is checked for the items accessed (for example, if an alias name is
mapped to a username but the username is not listed in ZNSUS, an error is
raised).
Catalog Operations
The basic NonStop ODBC Server catalog operations are: