Recommended Patches for CPU Resource Manager
(Doc ID 1339803.1)
Last updated on SEPTEMBER 27, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.3 [Release 10.2 to 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Details
This note lists the recommended patches for Oracle Database CPU Resource Manager. It supersedes MOS <Document 1207483.1>.
It applies to Oracle RDBMS Enterprise Edition, versions 10.2.0.4, 10.2.0.5, 11.1.0.7, 11.2.0.1, 11.2.0.2, and 11.2.0.3.
The Oracle Database Resource Manager can be used in many ways, such as managing CPU, I/O, parallel execution, runaway queries, etc. This note addresses issues that are specific to managing CPU. Refer Note 1484302.1 - Primary Note: Overview of Oracle Resource Manager
CPU Resource Manager is enabled when the current Resource Plan contains CPU management directives. These directives are called cpu_p1, cpu_p2, cpu_p3, etc. in releases prior to 11.1. They are called mgmt_p1, mgmt_p2, mgmt_p3, etc. in 11.1 and all subsequent releases.
When using CPU Resource Manager, 3 types of issues are seen:
(1) Excessive throttling, resulting in under-utilization of the CPU.
(2) Poor conformance to the Resource Plan.
(3) Crashes or internal errors.
Below is a list of the most critical, known bugs for CPU Resource Manager. These bug fixes are recommended for all customers that are either evaluating or using CPU Resource Manager.
For other recommended bug fixes, monitoring scripts, and other tips for Resource Manager, see the primary MOS <Document 1339769.1>.
|
Bug |
Bug Description |
Recommended Releases |
|
CONNECTION TIMEOUT WHEN RMAN BACKUP RUNING Resource Manager under-utilizes the CPUs. This bug occurs with workloads that contain a lot of sequential I/Os. |
10.2.0.4 |
|
|
Unpublished bug 8793492 |
INSTANCE CAGING LETS TOO MANY ORACLE FOREGROUND PROCESSES RUNNING PERIODICALLY The name for this bug is misleading, as it also occurs when Instance Caging is not used. The symptom is long wait times for "library cache: mutex X", resulting in excessive CPU utilization. |
11.1.0.7 |
|
Unpublished bug 6431266 |
TURN OFF QUANTUM DONATION: PLAN CONFORM DISPARITY + HIGH THRESHOLD BASED ON LOW This fix improves the accuracy with which Resource Manager enforces the resource allocations specified in the Resource Plan. |
10.2.0.4 |
|
Unpublished bug 8636407 |
INSTANCE CRASH DUE TO INTERNAL ERROR ENCOUNTERED BY PMON The symptom of this bug is ORA-600[kgskexitsch]. It is a very intermittent bug that can result in instance crashes. |
10.2.0.4 |
|
<Bug 10039731> |
HIGH WAITS FOR RUNNABLE PROCESS USING PX AND RESMGR Resource Manager under-utilizes the CPUs. This fix addresses the under-utilization. It also improves the accuracy with which Resource Manager enforces the resource allocations specified in the Resource Plan. |
11.2.0.1 (fixed in Exadata BP8) |
|
<Bug 8660422> |
SINCE APPLYING PATCH FOR 8624887 "UNSPECIFIED WAIT EVENT" IS SEEN IN AWR This bug causes Resource Manager to under-utilize the CPUs. This bug can also result in a large number of "unspecified" wait events. |
10.2.0.4 |
|
Unpublished bug 9924349 |
DBMV2: ORA 600 [RESPLAN:TRYADD_3] IN THE CELL SIDE WITH GE/DBFS WORKLOAD This bug only occurs on Exadata systems. The symptom is a storage cell crash with the error ORA 600 [RESPLAN:TRYADD_3]. The workaround is to avoid using Resource Plans with subplans, such as the "default_maintenance_plan", which is enabled during the maintenance windows. |
Exadata-only issue. |
|
Unpublished bug 10326338 |
HIGH RESMGR:CPU QUANTUM WITH APPSQOS_PLAN IN PLACE Resource Manager under-utilizes the CPUs. This bug can occur on with wait-intensive workloads (often OLTP databases) with any resource plan. |
10.2.0.4 |
|
Unpublished bug 11064851 |
CPU CONSUMED TIME DOES NOT TAKE ACCOUNT OF SHORT WAITS This bug only affects the Resource Manager statistics. The Resource Manager statistics for "cpu consumed" is too low. It doesn't include CPU consumed during short waits. |
11.2.0.1 |
|
Unpublished bug 7414919 |
CONSUMED_CPU_TIME IN SYS_GROUP IS INCORRECTLY REPORTED This bug only affects the Resource Manager statistics. The reported value of v$rsrc_consumer_group.consumed_cpu_time is too high. |
10.2.0.4 |
|
Unpublished bug 12420002 |
LNX64-11203-RAC:DB HIT ORA-700 [KGSKRECALC:RECALCRUNCOUNT1] This bug can cause intermittent errors. The symptoms of this bug are ORA-600 [kgskewtx] or ORA-700[kskplanresetact] or ORA-700 [kgskrecalc:recalcruncount1] or ORA-600[kgskrunnextint:state]. |
10.2.0.4 |
|
Unpublished bug 10219583 |
DBMV2: DATABASE HUNG AFTER 4 HRS OF ENABLE/DISABLE IORMPLAN This bug can cause the database to hang when when changing resource manager plans during heavy workload activity. This bug occurs very intermittently. |
Exadata-only issue. |
|
<Bug 16392079> |
SESSIONS HANG WAITING FOR 'RESMGR:CPU QUANTUM' When the VKRM background process is not present, processes can wait in the "resmgr:cpu quantum" wait event indefinitely. This bug occurs when the resource plan is enabled, disabled, and then re-enabled very quickly. |
11.2.0.1 |
|
<Bug 14389148> |
EXCESSIVE THROTTLING FOR OLTP WORKLOADS For workloads that are wait-intensive (short amounts of CPU usage followed by waits), Resource Manager can over-throttle the database, resulting in lower CPU utilization. This bug is highly recommended for 11.2.0.3 only. |
11.2.0.3 |
|
Unpublished bug 15844803 |
DYNAMIC THRESHOLD SET TO 2127 This bug can allow too many sessions to run concurrently if dynamic thresholds are enabled. This makes Instance Caging not work. |
11.2.0.3 |
|
INCREASED LATCH FREE WAITS ON RESMGR:SCHEMA CONFIG AFTER MOVE OF GSI TO M6 This bug occurs for workloads that heavily utilize parallel execution. It results in latch contention on "resmgr:schema config". |
11.2.0.3 11.2.0.4 |
Actions
Contacts
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
| Details |
| Actions |
| Contacts |
| References |