While Provisioning The Audit Settings on The Source Database Huge Trace Files Get Created (Doc ID 746503.1)

Last updated on JANUARY 13, 2009

Applies to:

Oracle Audit Vault - Version: 10.2.3 to 10.2.3
This problem can occur on any platform.

Symptoms

While provisioning or retrieving  the audit settings to/from the source database the agent's $ORACLE_HOME/av/log/agent.out or server's $ORACLE_HOME/<hostname>_<sid>/sysman/log/emdb.nohup files grow too much. They can consume up to 10GB in a couple of minutes. The only thing that's written is similar to :

08/10/30 13:36:23 COMPARE EVENT: event1= INSERT event2 = GRANT
08/10/30 13:36:23 COMPARE EVENT: event1= INSERT event2 = INSERT
08/10/30 13:36:23 COMPARE EVENT: event1= INSERT event2 = INSERT
08/10/30 13:36:23 COMPARE EVENT: event1= INSERT event2 = RENAME
08/10/30 13:36:23 COMPARE EVENT: event1= INSERT event2 = RENAME
08/10/30 13:36:23 COMPARE EVENT: event1= INSERT event2 = DELETE
08/10/30 13:36:23 COMPARE EVENT: event1= INSERT event2 = DELETE


or

08/10/31 08:13:53 <oracleDbAuditSetting type="PRIVILEGE" event="CREATE TRIGGER" returnType="BOTH" frequencyType="BY ACCESS" />

08/10/31 08:13:53 <oracleDbAuditSetting type="PRIVILEGE" event="CREATE ANY TRIGGER" returnType= "BOTH" frequencyType="BY ACCESS" />

08/10/31 08:13:53 <oracleDbAuditSetting type="PRIVILEGE" event="ALTER ANY TRIGGER" returnType="BOTH" frequencyType="BY ACCESS" />

08/10/31 08:13:53 <oracleDbAuditSetting type="PRIVILEGE" event="DROP ANY TRIGGER" returnType="BOTH" frequencyType="BY ACCESS" />



Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms