EM 13c: Multiple Composite Targets In "Status Pending (Post Blackout)" or in Status Pending
(Doc ID 2800739.1)
Last updated on SEPTEMBER 28, 2021
Applies to:
Enterprise Manager Base Platform - Version 13.4.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
Multiple Cluster ASM / Cluster Database targets stuck in status pending.
After creating a blackout and ending on these targets, these targets will go into "Status Pending (Post Blackout)".
EMDiag Target dump on any of these targets shows the following stack:
Error stack ORA-20233: ORA-20233: Parameter datatypes do not match ORA-06512: at "SYSMAN.EM_REP_METRIC", line 438
ORA-06512: at "SYSMAN.EM_REP_METRIC", line 1803
ORA-06512: at "SYSMAN.MGMT_TARGET", line 4407
ORA-06512: at "SYSMAN.EM_NG_SYSTEM", line 1639
ORA-06512: at "SYSMAN.EM_NG_SYSTEM", line 1861
ORA-06512: at "SYSMAN.EM_NG_SYSTEM", line 2317
ORA-06512: at "SYSMAN.EM_REP_METRIC", line 1803
ORA-06512: at "SYSMAN.MGMT_TARGET", line 4407
ORA-06512: at "SYSMAN.EM_NG_SYSTEM", line 1639
ORA-06512: at "SYSMAN.EM_NG_SYSTEM", line 1861
ORA-06512: at "SYSMAN.EM_NG_SYSTEM", line 2317
and / or
Availability metric collection : FAIL - Unable to get collection information
Availability metric errors : OK
Availability errors (History) : OK
Composite availability metric : FAIL - No composite metric definition found
Composite availability task : FAIL - No composite task definition found
Availability metric errors : OK
Availability errors (History) : OK
Composite availability metric : FAIL - No composite metric definition found
Composite availability task : FAIL - No composite task definition found
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |