NonStop SQL/MP Reference Manual

NonStop SQL/MP Reference Manual—142115
C-22
CLEANUP Exception Cases
object that depends on a collation but not the collation, CLEANUP purges the
dependent object and deletes the relationship to the collation.
•
CLEANUP and remote objects
CLEANUP cleans up objects only on the local node. To delete all partitions of a
damaged object distributed over several nodes, you must run CLEANUP on each of
the nodes involved.
CLEANUP Exception Cases
In certain situations (described in the following text) the catalog does not contain
enough information to enable CLEANUP to remove the catalog description of an SQL
object. In such cases, you can use a licensed SQLCI2 process to manually correct the
catalog and then rerun CLEANUP.
If CLEANUP is unable to remove an object's file label, you can use the GOAWAY
utility to remove the file label, but you should use GOAWAY only as a last resort.
Specifically, you cannot use CLEANUP to:
•
Purge a view when the entry for the view in the TABLES table cannot be accessed.
•
Purge a program when the entry for the program in the PROGRAMS table cannot be
accessed.
•
Purge an object that has no file label and no entry in the USAGES table.
•
Purge an object when the entry for the object's catalog in the VERSIONS table
cannot be accessed.
•
Purge a dependent object that you do not explicitly name in qualified-
fileset-list if USAGES table information about the object is missing or
inaccessible.
•
Purge a catalog's name entry in the system catalog's CATALOGS table when the
BASETABS and COLUMNS tables for the catalog are missing.
When purging a catalog, CLEANUP does not remove the catalog's name entry from
the system catalog CATALOGS table until the catalog's BASETABS or COLUMNS
table is purged. If, however, the BASETABS and COLUMNS tables are already
missing when you request the CLEANUP operation, CLEANUP removes the
remaining portion of the catalog but does not delete the name entry in the system
catalog's CATALOG table. To reuse the purged catalog's name, you must first
remove the orphan entry from the system CATALOGS table with a licensed
SQLCI2 process.
Caution. Never use the following command to purge SQL objects and catalogs:
SQLCI CLEANUP $*.*.*!, CATALOGS;
This command deletes all SQL objects and catalogs from a node, including the system catalog
and the $SYSTEM.SYSTEM.SQLCI2 program. If you want to remove NonStop SQL/MP from a
node, see the NonStop SQL/MP Installation and Management Guide for instructions.