Re: IP auditing for unsuccessful connections
From: Neil Chandler <neil_chandler_at_hotmail.com>
Date: Thu, 28 Apr 2011 18:14:33 +0100
Message-ID: <BLU0-SMTP2059F9DD0532C4BF01DBA06859B0_at_phx.gbl>
Dianna,
Date: Thu, 28 Apr 2011 18:14:33 +0100
Message-ID: <BLU0-SMTP2059F9DD0532C4BF01DBA06859B0_at_phx.gbl>
Dianna,
To use auditing you will need to set the init parameter Audit_trail=DB (or file)
Then set auditing on:
Audit session whenever not successful;
The output from failed connections can be seen in dba_audit_session.
You need to be careful regarding the growth of the underlying table SYS.AUD$, which is in the system tablespace by default.
There is a MOS article about moving it to a separate tablespace.
Turn off the auditing using the noaudit command.
Regards
Neil.
sent from my phone
On 28 Apr 2011, at 17:27, Dianna Gibbs <DIANNA.GIBBS_at_childrens.com> wrote:
> We have a new application that is multi-tiered with connections coming from many different windows and websphere servers.
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Apr 28 2011 - 12:14:33 CDT