The Oracle database has sophisticated auditing capabilities and can audit virtually any action within the database. Oracle9i introduces Fine Grained Auditing which allows auditing down to the column level in queries. The Oracle database auditing features and Oracle Applications auditing features are completely separate mechanisms.
By default, only “Instance Startup”, “Instance Shutdown”, and connections to the database with administrator privileges are audited. Usually only session and database user auditing are enabled.
In the init.ora file, set the audit_trail parameter to true and restart the database.
From the SYSTEM user in SQL*Plus, execute the SQL AUDIT commands that coincide with your requirements.
- Does not provide before and after values for column changes.
- Audits are at the SQL statement level, they do not reflect the resulting impact to individual records and columns within a table.
- Provides no standard reporting or access to data from a form.
- Resulting data in the SYS.AUD$ table is not “end user” ready.
- Because the table is owned by SYS, cannot provide an event based alert or notification to a user. (Cannot define a trigger on SYS tables.)