EM 13.3| EM_METRIC_KEYS_E Table Not Getting Purged
(Doc ID 2648409.1)
Last updated on APRIL 01, 2022
Applies to:
Enterprise Manager Base Platform - Version 13.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 13.3.0.0.0 version, Repository
EM 13.3| EM_METRIC_KEYS_E table not getting purged
On EM 13.3 with April 2019 PSU, Tables such as EM_METRIC_KEYS_E,EM_METRIC_KEYS_E,EM_VIOLATIONS_E,MGMT_LONG_TEXT_E and EM_METRIC_STRING_LATEST_E are not getting purged.
BEGIN
GC$OBJ_LOG.set_session_log_level(GC$OBJ_LOG.LEVEL_FINE);
emd_maintenance.purge_metric_dependencies
(p_bulk_size => 10000,
p_purge_targets => emd_maintenance.PURGE_ENABLED,
p_purge_old => emd_maintenance.PURGE_ENABLED,
p_purge_metrics => emd_maintenance.PURGE_ENABLED,
p_purge_keys => emd_maintenance.PURGE_ENABLED,
p_parallel => emd_maintenance.PURGE_ENABLED);
GC$OBJ_LOG.set_session_log_level(GC$OBJ_LOG.LEVEL_OFF);
END;
/
ERROR
-----------------------
Error report -
ORA-01403: no data found
ORA-06512: at "SYSMAN.EMD_MAINTENANCE", line 4922
ORA-06512: at "SYSMAN.EMD_MAINTENANCE", line 5164
ORA-06512: at line 3
01403. 00000 - "no data found"
*Cause: No data was found from the objects.
*Action: There was no data from the objects which may be due to end of fetch.
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 |