Database Utilities (MOSC)

MOSC Banner

Failed Logon Delay Causing Performance Hit (Doc ID 2246758.1) - caused by Oracle Trace File Analyzer

edited Oct 26, 2020 1:39PM in Database Utilities (MOSC) 1 commentAnswered ✓

Failed Logon Delay Causing Performance Hit (Doc ID 2246758.1)

reported each 30 seconds on 2 Oracle Databases Exadata Cloud Machine (Exadata Cloud@Customer) different versions as:

19.8.0.0 Transaction Processing

12.2.0.1.200714 Transaction Processing

On both DB on aud$ view USERID is reported as TFAINVALID and no TIMESTAMP but obviously TFAINVALID DB username does NOT exist.

On unified_audit_trail table:

DBUSERNAME      OS_USERNAME     AUDIT_TYPE      UNIFIED_AUDIT_POLICIES         ACTION_NAM RETURN_CODE EVENT_TIMESTAMP                                                               COUNT(*)
--------------- --------------- --------------- ------------------------------ ---------- ----------- --------------------------------------------------------------------------- ----------
TFAINVALID      oracle          Standard        ORA_LOGON_FAILURES             LOGON             1017 23-OCT-20 02.54.28.821687 PM                                                         1
TFAINVALID      oracle          Standard        ORA_LOGON_FAILURES             LOGON             1017 23-OCT-20 02.54.08.059594 PM                                                         1

If we stop Oracle Trace File Analyzer the failed attempts logon disappear and if we start the logon reappear.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center