This content has been marked as final. Show 2 replies
Just to make it clear: this is not an Audit Vault issue.
We can't tell the impact, once we don't know about your database.
When you set to 'audit all', you are auditing all objects and all users in the database.
When you set Audit_trail=db, you choose to record the audits in a table called aud$, and it has a lot of views:
When you set 'Audit_sys_operations=true' means that you are auditing sys user as well.
Hope that helps.
Edited by: BSalesRashid on 15/06/2012 06:15
1- audit_trail=db set all non sys audit record to data dictionary
(eg : aud$ but, sql_bind,sql_text columns of aud$ will not be populated if you set audit_trail=db, if required this audit info also then
set audit_trail=db_extended or db,extended )
2 - Audit_sys_operations=true will audit sys user activities and will be recorded in audit file located at audit_file_dest
3- SQL>Audit all; start audit all successful connected session ( audit record to respective datadictiories eg :dba_audit_session)
Note:all activities that are not audited when you specify Audit All,
so better to go for specific audit option(eg:SQL>audit delete on <tab> by access) to make sure that activities on obj audited