ODBC Server Reference Manual

Managing Customized Catalogs
HP NonStop ODBC Server Reference Manual—429151-002
7-24
USERCAT DEINSTALL Statement
If SYSCAT DEINSTALL succeeds, you must run SYSCAT INSTALL before the system
catalog can be run again against the NonStop ODBC Server. If SYSCAT DEINSTALL
fails for any reason, the NonStop ODBC Server customized system catalog is
unchanged.
If Catalogs Are Still Customized
If your system contains a customized user catalog, you will receive an error message,
and the SYSCAT DEINSTALL statement will not be executed. You must decustomize
all user catalogs before decustomizing the system catalog.
USERCAT DEINSTALL Statement
Use the USERCAT DEINSTALL statement to decustomize a NonStop SQL/MP catalog.
When you no longer need to access a catalog using the NonStop ODBC Server, you
can decustomize it. When you decustomize a catalog, the NonStop ODBC Server
mapping tables and views are erased, and the catalog is no longer available through
the NonStop ODBC Server. When you decustomize a catalog, you can also drop
objects created using the NonStop ODBC Server, drop the NonStop SQL/MP catalog,
or both.
USERCAT DEINSTALL has the following syntax:
catalog-name
specifies the name of the subvolume containing the NonStop SQL/MP catalog to
be decustomized. The catalog-name appears in Guardian format and can
include the node and volume.
If the specified subvolume does not contain a customized catalog, USERCAT
DEINSTALL generates warning messages that the mapping tables could not be
found.
If you omit catalog-name, the current subvolume is used.
RESTRICT
causes the catalog mapping tables to be dropped if, and only if, there are no user
objects created by the NonStop ODBC Server in the catalog. The underlying
NonStop SQL/MP table is unaffected. If you specify RESTRICT, you must also
specify catalog-name.
RESTRICT is the default.
USERCAT DEINSTALL [catalog-name
[ RESTRICT | CASCADE | CASCADE_NSSQL ]]