In the morning, the Provincial Social Security Project Team responded that the database had a system-type SQL statement, which occupied a lot of resources and seriously affected the database performance. The specific SQL statement is:
Select count (*) FROM MGMT_METRIC_DEPENDENCY_DETAILS DEP, MGMT_SEVERITY sev where dep. TARGET_GUID =: B5 and dep. METRIC_GUID =: B4 and dep. KEY_VALUE =: B3 and dep. EDEP_TARGET_GUID = SEV. TARGET_GUID and dep. EDEP_METRIC_GUID = SEV. METRIC_GUID and dep. DEP_KEY_VALUE = SEV. KEY_VALUE and sev. COLLECTION_TIMESTAMP BETWEEN: B2 AND: B1
After investigation, this problem should be Oracle OEMbug. metalink reference article ID: 330383.1
Solution:
1. As part of your weekly maintenance jobs for the Oracle Management Repository, run the following
Procedure to analyze all of the objects in the SYSMAN schema:
Exec dbms_stats.gather_schema_stats ('sysmanc ');