Last updated on JUNE 18, 2015
Applies to:Enterprise Manager Base Platform - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 12.1]
Information in this document applies to any platform.
UP alerts are being generated for a target database after a blackout ends in Enterprise Manager 126.96.36.199 Cloud Control.
Event reported time=Feb 7, 2014 9:40:33 PM MST
The availability dump shows that the below state change events:
<Document 1545566.1> - EM 12c : How to Collect a Dump of the Availability History of a Target with the EMDIAG Repvfy kit?
1-Up 07-FEB-2014 21:40:33
6-Unknown 07-FEB-2014 21:40:33 07-FEB-2014 21:40:33
2-Metric Error 07-FEB-2014 21:40:19 07-FEB-2014 21:40:33 0d00h00m14s
1-Up 07-FEB-2014 21:36:23 07-FEB-2014 21:40:19 0d00h03m56s
6-Unknown 07-FEB-2014 21:36:20 07-FEB-2014 21:36:23 0d00h00m03s
5-Blackout 07-FEB-2014 21:23:06 07-FEB-2014 21:36:20 0d00h13m14s
Blackout ended at 07-FEB-2014 21:36:20
DB was in unknown status from 07-FEB-2014 21:36:20 To 07-FEB-2014 21:36:23
DB was marked in UP at 07-FEB-2014 21:36:23
DB was again marked as 'Metric Error' from 07-FEB-2014 21:40:19 To 07-FEB-2014 21:40:33
After this DB was marked as UP again at 07-FEB-2014 21:40:33
The .../agent_inst/sysman/log/gcagent.log file has this entry:
2014-02-07 21:40:19,829 1622104:F4E4536A:GC.SysExecutor.361 (CollectionManager.ResponseChecker) WARN - Response metric for target oracle_database.mydatabase being placed in metric collection error due to Response metric failed to run on schedule - likely due to validIf
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