ORA-12751: "Cpu Time Or Run Time Policy Violation" Reported Due to DBMS_FEATURE_AWR Running Slow on 12c
(Doc ID 2095583.1)
Last updated on MAY 12, 2022
Applies to:
Oracle Cloud Infrastructure - Database Service - Version N/A and laterOracle Database Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
- MMON workers fail with ORA-12751: "Cpu Time Or Run Time Policy Violation". This may be reported in trace and the alert log.
- Upon tracing, we see that the following query run by DBMS_FEATURE_AWR is long running, the query also runs slowly in SQL*Plus:
- The elapsed time of the query depends on the retention period and the interval settings of the AWR snapshots. In this case, we had a 90 days retention with a 30 minutes interval, which led to over 4000 snapshots. If the retention is lower, the query is faster.
- Gathering statistics on the AWR tables did not help
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |