Database activity monitoring (DAM) : Displaying the history of issued audit commands : Oracle audit management
 
Oracle audit management
The Target’s Audit Management page for Oracle target databases displays the history of issued audit commands.
Statement options
The Statement options section displays:
Database User
Audit Option
Success
Failure
Object options
The Object options section displays all the audit commands, including success or failure, for each object with:
Object owner
Object name
Object type
Access or Session on SELECT/INSERT/UPDATE/DELETE/EXECUTE/ALTER
To update the list, click the Refresh button.
Clearing audit settings
FortiDB modifies the Oracle auditing system to monitor the policies that you define. These audit settings affect what is audited and affect how fast the SYS.AUD$ table will fill. Under normal operating conditions, FortiDB removes its settings when monitoring is stopped.
However, sometimes the SYS.AUD$ table can become cluttered with other peoples' settings that were not properly removed. To correct this, use FortiDB's clear audit setting feature to remove all audit settings.
If FortiDB is the only client of the audit system, then you can use this feature to clear all audit settings. But if other people need the audit settings, do not clear audit settings. To clear audit settings, you must stop monitoring. After clearing the settings, the audit statement and audit options tables will be empty. If you then start FortiDB monitoring ,you will see only FortiDB's audit settings that are necessary for enabled policies.
Audit management
When using the audit-based collection methods for Oracle, you may want to clear the audit settings from previous operations if FortiDB is used as the exclusive auditing mechanism for that target database. Also, for the DB,EXTENDED collection method, you may want to delete all previous log entries in the Oracle target database. You can do both in the Audit Settings Management section of the Audit Management tab. These options are selected by default, so be sure to deselect these options if FortiDB is not the only service that is using Oracle's auditing mechanism.
For the DB,EXTENDED collection mechanism, the audit log table may periodically grow larger than the file system's capacity for that table. To periodically delete audit log entries, go tothe Scheduled Maintenance section.
Warning: Using FortiDB to manage the contents of the SYS.AUD$ should be compliant with the best practices of your organization.