"support clean DAM_data: A way to manually purge database activity monitoring data. Use this command only when absolutely necessary. Consult with Technical Support before you run this command. A Warning message and a confirmation step are included in the command. Syntax: support clean DAM_data < purge_type > < start_date > < end_date > . purge_type options: agg, exceptions, full_details, msgs, constructs, access, policy_violations, parser_errors, flat_log. start_date and end_date: YYYY-mm-dd."
This is the emergency purge for the monitoring tables that hold access records, constructs, exceptions and violations. A typical use is a full disk, when scheduled purge cannot free space fast enough.
A: support optimize tables < db > < table > reclaims space and reorganizes a table. It does not delete data.
C: support clean audit_results < rows > removes audit-process results.
B: support clean TURBINE is not a valid command.
Related commands: support show db-status used % and support show db-top-tables all locate the largest tables, and support clean log_files and support show large_files handle log files.
Services stopped on a full disk: After space is recovered, run restart stopped_services .
Preferred approach: Regular scheduled archive and purge, as in Question 55.