EM 12c, EM 13c: Troubleshooting Incorrect ASM or ASM Cluster Target Status in Enterprise Manager 12c and 13c Cloud Control
(Doc ID 1992791.1)
Last updated on NOVEMBER 06, 2019
Applies to:Enterprise Manager for Oracle Database - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 12.1]
Information in this document applies to any platform.
To show how the availability status for the ASM and Cluster ASM status is calculated, and to provide troubleshooting steps to follow, when the status shown in Enterprise Manager (EM) 12c and 13c Cloud Control is incorrect.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Check Your ASM Version|
|About the ASM Status|
|About the Cluster ASM Status|
|Section A - Information to gather if ASM Instance is showing wrong status|
|Step 1) Find the name of the ASM target|
|Step 2) Find out the 'real time' results of the 'Response' metric.|
|a) If a 1 is returned and you believe that this is the correct status|
|b) If a '1' is returned but you believe that this is not the correct status|
|c) If a '0' is returned' (accompanied by Ora-1017 or 1031)|
|d) If a '0' (accompanied by other ora-error message) is returned|
|e) If the message "the osm_target <name> does not exist" is returned|
|Step 3) Check the severity state that the agent has obtained for the Response Metric|
|If the Response Status is 'CLEAR'|
|If the Response Status is 'CRITICAL'|
|If the Response Status is Undetermined or unknown|
|Step 4) Confirm that the metric is scheduled|
|If the metric is not scheduled, force it to run|
|If the metric is still not scheduled, check for suspended metrics from the console|
|If the metric is scheduled, but is due to run more than 5 minutes in the future|
|Step 5) Make sure that the agent can upload to the OMS|
|If the agent can upload successfully|
|If the agent cannot upload successfully|
Section B - Cluster ASM