My Oracle Support Banner

Performance: CLOB and BLOB Columns Not Released At The Tablespace Level After Audit Data Truncated. (Doc ID 579087.1)

Last updated on OCTOBER 02, 2020

Applies to:

Oracle Warehouse Builder - Version 10.2 to 11.2.0.4 [Release 10.2 to 11.2]
Information in this document applies to any platform.

Goal

After audit data was purged by execution of purge_audit_template.sql script or truncated following note 'How To Purge OWB Execution Audit Tables Using The Truncate Command' (Doc ID 430755.1), there are no records in the wb_rt_audit_scripts table.  However, some CLOB and BLOB columns are not released at the  tablespace level.

Support aware of following CLOB and BLOB columns in OWBSYS schema:


owb$wb_rt_audit_params.clob_value              clob
owb$wb_rt_audit_execution.task_input           clob
owb$wb_rt_audit_executions.binary               blob
owb$wb_rt_audit_executions.description         clob
owb$wb_rt_audit_executions.client_info          clob
owb$wb_rt_audit_executions.metadata_info    clob
wb_rt_audit_script.script                                clob
wb_rt_ht_audit_file.file_text                           clob
owb$wb_rt_platform_files.text                        clob
owb$wb_rt_platform_files.binary_data            blob
owb$wb_rt_audit_files.file_text                       clob
owb$wb_rt_audit_files.file_binary                   blob

There are may be other tables in OWBSYS schema that contain columns with LOB type datatypes. 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.