SQL/MX 3.2.1 Reference Manual (H06.26+, J06.15+)

SQL/MX Utilities
HP NonStop SQL/MX Release 3.2.1 Reference Manual—691117-005
5-4
Considerations
options
determines how the CLEANUP operation is performed.
-r restricts the CLEANUP operation for the specified object. If the object has
dependent objects, the CLEANUP operation fails with an error. If no options are
specified, the default is -r.
-c cascades the CLEANUP operation for dependent objects. The dependent
objects are cleaned up along with the specified object.
input-filename
is the OSS file name of a file generated as a result of running the mxtool
VERIFY operation with the -oo option. This file contains the Guardian file
names of orphaned partitions to be removed.
guardian-physical-filename
is a single Guardian file name of a single orphaned cleanup partition. The node
name part is optional.
output-filename
is the OSS path name of the file to which the utility writes the log output. The
CLEAR option clears the file before logging the output. If CLEAR is omitted, and if
the log file exists, output is appended to the existing data in the file. The output-
filename cannot have a , (comma) or ; (semicolon).
Considerations
•
The CLEANUP operation for a single object can be performed by the schema
owner, object owner, or Super ID. The cleanup of orphaned objects can only be
performed by the Super ID.
•
The CLEANUP operation is used when standard DROP requests fail because of
metadata inconsistencies. The CLEANUP operation removes the objects when:
°
The metadata for the object exists and is available, but one or more partitions
are physically missing (dangling partition references)
°
One or more partitions physically exist, but the metadata for the object is
missing (orphaned partitions)
•
The CLEANUP operation creates a log file with details of the outcome. If outinfo
is not specified, a log file with a name in the format of LOG_weekday_month_day
of month_time_year is created in the current working directory.
•
The cleanup of an object with dangling partition references requires the following to
be present in the metadata:
°
Catalog information for the object’s catalog in the CATSYS and
CAT_REFERENCES tables in the system schema