Re: What happens to Oracle when sys.aud$ table or Oracle OS Audit file reaches storage capacity?

From: <TESTAJ3_at_nationwide.com>
Date: Fri, 26 Feb 2010 10:45:58 -0500
Message-ID: <OFF96A2E25.57C4A742-ON852576D6.005688C9-852576D6.00569B48_at_lnotes-gw.ent.nwie.net>

Well in the past, i've seen when writing for OS level auditing, the alert.log will get an entry about "not being able to write to adump destination" and continue on its way.

joe

---

Joe Testa, Oracle Certified Professional Senior Engineering & Administration Lead
(Work) 614-677-1668
(Cell) 614-312-6715

From:
"Arnold, Sandra" <ArnoldS_at_osti.gov>
To:
"'oracle-l_at_freelists.org'" <oracle-l_at_freelists.org> Date:
02/26/2010 10:44 AM
Subject:
What happens to Oracle when sys.aud$ table or Oracle OS Audit file reaches storage capacity?
Sent by:
oracle-l-bounce_at_freelists.org

I am writing an Oracle Security Test plan. One of the controls requires Oracle to stop processing transactions if the Oracle OS Audit files or the sys.aud$ table reaches storage capacity. I cannot find any documentation that lets me know what happens to Oracle when this occurs. Does Oracle react the same way as when the Archive Log area reaches storage capacity? The version of Oracle that I am using is 11.2.0.1 on Linux x86-64.  

Thanks,

Sandra Arnold
Sr. Database Administrator
OSTI/DOE
Oak Ridge, TN

--
http://www.freelists.org/webpage/oracle-l

Received on Fri Feb 26 2010 - 09:45:58 CST