EM13c: After RU23 DBMS Job Invalid Schedule for Exadata Fleet Tables Refresh crossed the critical threshold (INVALID)
(Doc ID 3054815.1)
Last updated on FEBRUARY 20, 2025
Applies to:
Enterprise Manager for Exadata - Version 13.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
In EM 13.5, after apply RU 23, "Exadata Fleet Tables Refresh" DBMS job remains in INVALID state and following incident has been raised
"DBMS Job Invalid Schedule for Exadata Fleet Tables Refresh crossed the critical threshold (INVALID). Current value: INVALID"
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 |