My understanding is that AUD$ table is not special in the sense that recording audit information in AUD$ also creates redo and undo in the redo logs. See, for example, Jonathan Lewis's post at http://jonathanlewis.wordpress.com/2011/06/07/audit-excess/. Therefore, deleting from AUD$ using regular SQL deletes also requires undo and redo. Why not export and truncate the AUD$ table (at the risk of losing a few records because of timing)? Could the AUD$ table be partitioned by date range? Could AUD$ be made a synonym if not licensed for partitioning? For example, the synonym AUD$ could be pointed to an underlying table called AUD20130101$ on Jan 1 and to AUD20130102$ on Jan 2. Kindest regards, Iggy -- Iggy Fernandez Email: iggy_fernandez@xxxxxxxxxxx Cellphone: (925) 478 3161 Blog: So Many Manuals So Little Time Author of Beginning Oracle Database 11g Administration Editor of the NoCOUG Journal > I've used the info in this pythian blog with great success at various sites > to purge the audit table. > http://www.pythian.com/news/1106/oracle-11g-audit-enabled-by-default-but-what-about-purging/ > Be careful how much data you will purge the first time. Purge the data > first then move to a new tablespace. -- //www.freelists.org/webpage/oracle-l