Status of HAS target type for Oracle Restart is shown as metric collection error in 12c
(Doc ID 1563118.1)
Last updated on FEBRUARY 20, 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.
* Discovering an Oracle High Availability Service for Oracle Restart (Oracle Grid Infrastructure for a Standalone Server) gives following errors in 12c Cloud Console:
The following warnings are detected. Are you sure you want to save the cluster target 'has_oraclemac1' anyway?
oraclemac1 - No Oracle High Availability Service is detected on the host.
Also an already discovered Oracle High Availability Service for Oracle Restart is shown as metric collection error
During Discovery, following errors are seen in emagent_perl.trc at AGENT_INST/sysman/log folder:
cluster.pl: Wed Jun 12 18:12:49 2013: DEBUG: CLUSTER_HAS_DISCOVERY: emdRoot=<PATH>/agent12g/core/188.8.131.52.0
cluster.pl: Wed Jun 12 18:12:49 2013: DEBUG: CLUSTER_HAS_DISCOVERY: crsHome is picked from the environment CRS_HOME as /u01/184.108.40.206/grid
cluster.pl: Wed Jun 12 18:12:49 2013: INFO: CLUSTER_HAS_DISCOVERY: ERROR:emcrspmain:procr_init_ext:cluster API error:Failed to initialize ctx with ocrctx 32 PROC-32: Cluster Ready Services on the local node is not running Messaging error [gipcretConnectionRefused
For a target that is already discovered which has metric collection error shows:
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