This sounds like you are having active databases with lots of activity or data changes for which you have enabled the auditing. To control the volume of audit data you can narrow the scope of events that you want to audit and/or setup automate purge procedures that delete old audit records. Both options are available in DB Audit GUI. : I noticed my repository database has grown to about 19Gb. On this server, I : have 35 databases, not including the system dbs. The table that has grown : is sys_audit_trail. Although there are 35 databases on this server, I am : only monitoring 3 but plan to expand this number. I don't know if the size : and lack of indexes are the but any sys_audit report takes a long time (if : ever) to return. Currenly there are almost 30 million rows in this table. : I understand that I can truncate the table, but what will that do to any : history I want to recover?
|