Last updated on JUNE 29, 2017
Applies to:Enterprise Manager for Oracle Database - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 12.1]
Information in this document applies to any platform.
This article applies to Enterprise Manager (EM) 22.214.171.124 to 126.96.36.199 Cloud Control. Starting with version 188.8.131.52, the server generated alert system is not relied upon as a basis for alerting (for any metric for which it is possible to set a threshold for).
Whenever a target database is in metric collection error or down (wrong password, unconfigured, stopped, etc) status, changing the metric collection settings are updated in the repository but are not being propagated to dba_thresholds of the target due to its state. This is creating a discrepancy between the threshold values in the repository for that target and what is stored in the target's dba_thresholds. Also, in cases where there are errors when saving to the DB server side (dba_thresholds), these are not being returned to the user.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms