Setting it does not cause any audit records to be written.
An exception to that might be if the audit command was used prior to
setting audit_trail, in which case auditing will start working when
the new setting takes effect.
Check the 11g docs - there is a security guide with a lot of info on this.
On 10/27/08, Newman, Christopher wrote:
If using a pfile, what goes in sys.aud$ when audit_trail is set to DB?
We ran into a scenario where we want to change auditing on a DB, but the
pfile has audit_trail=NONE, hence we have to bounce. I think if we set
it to DB across the enterprise, we can turn auditing on and off at will
via the 'AUDIT XXX' command. Does setting this parm to DB have any
effect other than allowing you to turn auditing on and off, and
directing the audited information to sys.aud$? Does simply setting it
to 'DB' cause info to go in the sys.aud$, even if you haven't enabled
auditing?
Thanks- Chris
--
http://www.freelists.org/webpage/oracle-l
--If using a pfile, what goes in sys.aud$ when audit_trail is set to DB?
We ran into a scenario where we want to change auditing on a DB, but the
pfile has audit_trail=NONE, hence we have to bounce. I think if we set
it to DB across the enterprise, we can turn auditing on and off at will
via the 'AUDIT XXX' command. Does setting this parm to DB have any
effect other than allowing you to turn auditing on and off, and
directing the audited information to sys.aud$? Does simply setting it
to 'DB' cause info to go in the sys.aud$, even if you haven't enabled
auditing?
Thanks- Chris
--
http://www.freelists.org/webpage/oracle-l
Sent from Gmail for mobile | mobile.google.com
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
--
http://www.freelists.org/webpage/oracle-l
