SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual—523352-013
P-35
Considerations—PURGE
indexes that depend on the table, and all views that depend on the table except
dependent shorthand views for which you lack purge authority. SQL invalidates the
latter.
To purge a protection view, all partitions of the view, all views and SQL program
files that depend on the view, all partitions of the table that the view depends on,
and all partitions of all indexes on that table must be available. When you purge a
view, SQL also purges all views that depend on the purged view, except for
dependent shorthand views for which you do not have purge authority. SQL
invalidates the latter.
To purge a collation, you must also purge objects that depend on the collation. If
you purge a collation and a table or index that depends on the collation in the
same PURGE operation, PURGE deletes the table or index before the collation.
An error occurs if you attempt to purge the collation without purging dependent
objects.
To purge shadow labels, you must be the local super ID.

PURGE invalidates any SQL program files that depend on the SQL objects
purged.

You can use PURGE within a user-defined TMF transaction unless the command
purges a nonaudited object or a shadow label. If PURGE fails within a user-defined
transaction, the entire PURGE operation is undone.
If you use PURGE outside of a user-defined TMF transaction, SQL automatically
begins a system-defined transaction for the purge of each audited SQL object in
qualified-fileset-list. If PURGE fails, only the system-defined transaction
in progress at the time of the failure is undone. (SQL does not begin a
system-defined transaction for an Enscribe file, even if the file is audited.)
If you press the Break key to interrupt a PURGE operation, SQL reports the last
object purged at the time you issued the break request and also completes (but
does not report) the purge of the next object to be purged. If a user-defined TMF
transaction is not in progress, all changes are committed. If a user-defined
transaction is in progress, the transaction is rolled back and all changes are
undone.
After pressing the Break key, you can restart the PURGE by reentering the
command or by using the FC command. This sequence is permissible:
>> PURGE *.*.* FROM CATALOG $VOL1.SUBV1;
>> (press the Break key)
>> PURGE *.*.* FROM CATALOG $VOL1.SUBV1;
PURGE operations that involve many partitions, especially remote partitions, can
often cause many occurrences of error 73 (The disk file or record is locked) or
error 40 (The operation timed out) when the operation attempts to update file
labels and catalog entries.