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

From: Newman, Christopher <cjnewman_at_uillinois.edu>
Date: Fri, 26 Feb 2010 09:45:10 -0600
Message-ID: <565F609E6D736D439837F1A1A797F341020CD31A_at_ADMINMAIL1.ui.uillinois.edu>



If you have auditing enabled and set to DB, users will not be able to login to the database as they will not be able to write to the sys.aud$ table.  
  • Chris

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Arnold, Sandra Sent: Friday, February 26, 2010 9:43 AM
To: 'oracle-l_at_freelists.org'
Subject: What happens to Oracle when sys.aud$ table or Oracle OS Audit file reaches storage capacity?  

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:10 CST

Original text of this message