AUD: Audit Commit&nbsp…

 Aud: Audit Commit Delay Exceeded, Written A Copy To Os Audit Trail [ID 788530.1] 转到底部 

--------------------------------------------------------------------------------

修改时间:2012-6-12类型:PROBLEM状态:PUBLISHED优先级:3 注释 (0)    
 

In this Document
 Symptoms
 Changes
 Cause
 Solution
 References

 

--------------------------------------------------------------------------------

Applies to:
Oracle Server - Enterprise Edition - Version 10.2.0.3 to 11.2.0.1 [Release 10.2 to 11.2]
Information in this document applies to any platform.
Checked for relevance on 17-Sep-2011

 

Symptoms
You see the following messages appear in your alert.log:

 

AUD: Audit Commit Delay exceeded, written a copy to OS Audit Trail
Changes
You have applied the Audit Cleanup Patch or any superceding patch as referenced from note 731908.1.

Cause
This is a change that was introduced within the audit functionality to support Audit Vault, these messages can appear in your alert.log occasionally

even if this database is not a source of Audit Vault, the reason is as follows:

The database will guarantee that the transaction writing the audit record will commit within a pre-defined maximum allowed interval which

is called the Audit Commit Delay interval. If the transaction takes more than Audit Commit Delay to commit the audit record,

the Database will write the same record to the OS audit trail. This is a fallback mechanism to make sure there's always written evidence

of an audited action within the defined timeframe, a such it is a feature to enhance audit security.

The commit delay is fixed at 5 seconds and cannot be tuned.

Solution
The problem is happening because the audit functionality was not able to commit an audit record within 5 seconds, this means at the time the message

was written to the alert.log your database was under stress. The cause of the problem is not the auditing layer and the messages seen in the alert.log

are only showing that the auditing is suffering because of the generic performance problems of the environment which might

affect other components as well.

These messages are purely informational and no direct action can or should be taken to avoid them. This is most likely because of a resource problem on your database. If this is seen incidental you can ignore it but if these messages are seen regularly you will likely have a resource problem and also seeing other symptoms of that, you should analyze and solve the generic performance problem first and then these messages will also go away.

Update: the fix to unpublished bug 8642202 changes the behaviour as follows:

Audit Commit Delay increased to 15 seconds and enforced only when AUD$ is initialized for cleanup.

So if you have the fix to Bug 8642202, the delay will be increased to 15 seconds and if you still get these messages and you don't want them

and you are not using package DBMS_AUDIT_MGMT for cleanup, you can now disable this security feature by calling:

 

set serveroutput on
begin
   if dbms_audit_mgmt.IS_CLEANUP_INITIALIZED(
      audit_trail_type => DBMS_AUDIT_MGMT.AUDIT_TRAIL_AUD_STD) then
      dbms_audit_mgmt.DEINIT_CLEANUP(
      audit_trail_type => DBMS_AUDIT_MGMT.AUDIT_TRAIL_AUD_STD);
      dbms_output.put_line('DEINIT_CLEANUP for AUDIT_TRAIL_AUD_STD');
  end if;
end;
/

This may alleviate the problem in some cases but there can still be an underlying performance problem.

Bug 8642202 is fixed in patchset 10.2.0.5, PSU 11.2.0.1.1 and patchset 11.2.0.2 and future releases.

Merge patches that include this fix:

11.1.0.7: Patch 9821987

On Windows this is fixed in 11.1.0.7 patch bundle 40 and higher, see Note 161549.1 for more info.

References
@ BUG:8642202 - LX64: TOO MANY AUDIT FILES GENERATED, 500,000 AUD FILES AFTER 2 DAYS
NOTE:161549.1 - Oracle Database, Networking and Grid Agent Patches for Microsoft Platforms
NOTE:731908.1 - New Feature DBMS_AUDIT_MGMT To Manage And Purge Audit Information
NOTE:8642202.8 - Bug 8642202 - Lots of audit files due to "Audit Commit Delay exceeded"