Neoview SQL Reference Manual (R2.2)

PURGEDATA Utility
• “Syntax Description of PURGEDATA”
• “Considerations for PURGEDATA”
• “Examples of PURGEDATA”
The PURGEDATA utility deletes all data from a Neoview SQL table and its related indexes.
PURGEDATA table [IGNORE_TRIGGER] [NOLOG]
Syntax Description of PURGEDATA
table
is the name of the table from which to purge the data. See “Database Object Names” (page 196).
Considerations for PURGEDATA
• You must have ALL privileges on the table.
• table-name can be either a table name or a materialized view name.
• If table-name is a materialized view name, the IGNORE_TRIGGER is not supported and
will be ignored if specified.
• If the NOLOG option is not specified, an error is returned if PURGEDATA tries to purge a
table that has a materialized view defined on it.
• If the NOLOG option is not specified, an error is returned if PURGEDATA tries to purge a
materialized view that has a materialized view defined on it.
• Errors are returned if table cannot be accessed or if a resource or file system problem causes
the delete to fail.
• PURGEDATA returns an error if a user transaction exists.
• PURGEDATA sets the corrupt bit while processing. If PURGEDATA fails before it completes,
the table and its dependent indexes will still be corrupt and you must contact HP support
to complete the operation and remove the data. A file system error is returned when it tries
to open a table whose corrupt bit is set.
Examples of PURGEDATA
• This example purges the data in the specified table. If the table has indexes, their data is also
purged.
PURGEDATA myschema.mytable;
PURGEDATA Utility 187