EM 13c: "Failed Logins" and "Failed Logins (Historical)" Metrics Keep Running in Database Despite Being Disabled (Doc ID 2459666.1)

Last updated on DECEMBER 12, 2023

Applies to:

Symptoms

The "Failed Logins" and "Failed Logins (Historical)" database metrics continue to run despite being disabled in the database target.

The Top Activity page of the respective database target may show the following query being executed:

SELECT TO_CHAR(TO_TIMESTAMP('2017-10-01' , 'YYYY-MM-DD') AT TIME ZONE 'GMT', 'YYYY-MM-DD HH24:MI:SS TZD') AS curr_timestamp, SUM(failed_count) AS failed_count
FROM (
SELECT COUNT(username) AS failed_count
FROM sys.dba_audit_session
WHERE returncode != 0 AND TO_CHAR(CAST(timestamp AS DATE) , 'YYYY-MM-DD') >= '2017-10-01' AND TO_CHAR(CAST(timestamp AS DATE) , 'YYYY-MM-DD') < TO_CHAR((TO_DATE('2017-10-01', 'YYYY-MM-DD') + 1), 'YYYY-MM-DD') UNION
SELECT COUNT(DBUSERNAME) AS failed_count
FROM sys.unified_audit_trail
WHERE ACTION_NAME='LOGON' and return_code <> 0 AND TO_CHAR(CAST(event_timestamp AS DATE) , 'YYYY-MM-DD') >= '2017-10-01' AND TO_CHAR(CAST(event_timestamp AS DATE) , 'YYYY-MM-DD') < TO_CHAR((TO_DATE('2017-10-01', 'YYYY-MM-DD') + 1), 'YYYY-MM-DD'))

This query indicates that these metrics are indeed being collected and might cause performance issues in the database target.

Refer to the following screen shots, as example showing the metrics as disabled:

In Metric and Collection Settings -> All Metrics

In Metric and Collection Settings -> Other Collected Items

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.