Re: OEM reporting failed login attempts on read-only physical standby database

From: Douglas Dunyan <dmdunyan_at_gmail.com>
Date: Sat, 25 Jun 2022 20:34:07 -0700
Message-ID: <CA+UckTsyeJNbYTVH-Vmp0O9_Ypfuc-e5BkPTabao6u2sVQsqvg_at_mail.gmail.com>



Hmmm...
Audit session whenever not successful;

https://www.netwrix.com/how_to_track_down_failed_oracle_logon_attempts.html

D

On Fri, Jun 24, 2022, 2:21 AM DOUG KUSHNER <dougk5_at_cox.net> wrote:

> The database in question is an 11.2.0.4 2-node RAC *read-only standby*
> database on Exadata, Starting this evening, OEM began raising 'Event
> name=audit_failed_logins2:failed_login_count', reporting hundreds of failed
> login attempts. Of course OEM does not provide any additional information,
> so it remains a mystery.
>
> The primary and standby databases are both auditing failed connections, so
> I searched through the *.aud files on both nodes of the standby database
> and didn't find any clues.
>
> What should we check next?
>
> Regards,
> Doug
>
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Sun Jun 26 2022 - 05:34:07 CEST

Original text of this message