Resmgr:Cpu Quantum 等待事件

关闭Resmgr:Cpu Quantum

alter system set resource_manager_plan='' scope=both sid='*'; 

execute dbms_scheduler.set_attribute('SATURDAY_WINDOW','RESOURCE_PLAN',''); 
 execute dbms_scheduler.set_attribute('SUNDAY_WINDOW','RESOURCE_PLAN',''); 
execute dbms_scheduler.set_attribute('MONDAY_WINDOW','RESOURCE_PLAN',''); 
 execute dbms_scheduler.set_attribute('TUESDAY_WINDOW','RESOURCE_PLAN',''); 
execute dbms_scheduler.set_attribute('WEDNESDAY_WINDOW','RESOURCE_PLAN',''); 
 execute dbms_scheduler.set_attribute('THURSDAY_WINDOW','RESOURCE_PLAN',''); 
execute dbms_scheduler.set_attribute('FRIDAY_WINDOW','RESOURCE_PLAN',''); 

Resource Manager Plan Changes Settings Every Week (文档 ID 759503.1)

转到底部

---

In this Document Goal   Solution This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. APPLIES TO: Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.1 [Release 10.2 to 11.2] Information in this document applies to any platform. *** Checked for relevance on 05-Apr-2016 *** GOAL Detailed description with Example ---------------------------------- 1) Noticed that the resource manager plan was set to "resource_manager_plan string SCHEDULER[0x22BB]:SYSTEM_PLAN". 2) Changed this using the command ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = '' SCOPE=BOTH; 3) Every week when checking on this database setting it goes back to the setting "SCHEDULER[0x22BB]:SYSTEM_PLAN". I keep having to issue the following command, but the resource manager plan keeps changing back ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = '' SCOPE=BOTH; The database is not being recycled so why is the setting changing. It is causing performance issues every time it changes back. What could cause this setting to change back? SOLUTION It is possible that the scheduler windows are altering the resource plan. A scheduler window can have a resource plan associated with it. The default plan associated with default weekend and weeknight windows is the system_plan. You can see that by looking at the following view: select * from V$RSRC_PLAN_HISTORY order by SEQUENCE#; To set the resource plan such that the scheduler cannot alter the plan, do the following: ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = 'FORCE:Desired_Resource_Plan' scope=both; OR ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = 'FORCE:' scope=both; --> For Null OR Change the active windows to use the null resource manager plan (or other unrestrictive plan) using: execute dbms_scheduler.set_attribute('WEEKNIGHT_WINDOW','RESOURCE_PLAN',''); --And execute dbms_scheduler.set_attribute('WEEKEND_WINDOW','RESOURCE_PLAN',''); (execute the same for any other scheduler windows that exist, changing the window name). From there on, the scheduler windows will not be able to change the resource plan. The active resource plan can be shown by: select * from v$rsrc_plan; Large Waits With The Wait Event "Resmgr:Cpu Quantum" (文档 ID 806893.1) 转到底部 In this Document Symptoms   Cause   Solution   References This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. APPLIES TO: Oracle Database - Enterprise Edition - Version 10.2.0.3 to 11.2.0.3 [Release 10.2 to 11.2] Information in this document applies to any platform. NOTE: A complete list of patches required to address this problem is maintained by the resource manager product team in Note 1339803.1 - Recommended Patches for CPU Resource Manager SYMPTOMS High waits on wait event 'resmgr:cpu quantum', while there is no CPU load on the host. Top 5 Timed Events ~~~~~~~~~~~~~~~~~ Event                   Waits   Time(s) Avg Wait(ms) % Total CallTime WaitClass resmgr:cpu quantum      247074   4036            16              58.3 Scheduler CPU time                3201       46.3 log file sync           225905    808             4              11.7 Commit db file sequential read 95930     650             7               9.4 User I/O log file parallel write 235251    569             2               8.2 System I/O CAUSE Related software defects : Bug 8221960 - WAITS FOR "RESMGR CPU QUANTUM" Bug 7527260 - HIGH WAIT EVENTS ON "RESMGR CPU QUANTUM" WHEN RESOURCE MANAGER IS ENABLED Unpublished Bug 10326338 - HIGH RESMGR:CPU QUANTUM WITH APPSQOS_PLAN IN PLACE Bug 7510766 - RESOURCE MANAGER IS OVER THROTTLING Bug 8660422 - "unspecified wait event" and/or "ksfd: async disk IO" after applying patches that include fix for Bug 7510766 Bug 6874858 - Poor performance with Resource Manager when RMAN is running Bug 16392079 -SESSIONS HANG. WAITING FOR 'RESMGR:CPU QUANTUM' SOLUTION Bug 8221960 - WAITS FOR "RESMGR CPU QUANTUM" One-off patches available  Patch 8221960 Bug 7510766 - RESOURCE MANAGER IS OVER THROTTLING Fixed in 11g Release2 and included in patchset 10.2.0.5 The fix of Bug 7510766 can cause a regression ( Bug 8660422 - "unspecified wait event" and/or "ksfd: async disk IO" after applying patches that include fix for Bug 7510766) Apply  Patch 8660422 Unpublished Bug 10326338 - HIGH RESMGR:CPU QUANTUM WITH APPSQOS_PLAN IN PLACE One-off patches available  Patch 10326338 Bug 7527260 - HIGH WAIT EVENTS ON "RESMGR CPU QUANTUM" WHEN RESOURCE MANAGER IS ENABLED          Fixed in patchset 10.2.0.4 Workaround by setting the parameters : _enable_NUMA_optimization=FALSE  _db_block_numa=1 Bug 6874858 - Poor performance with Resource Manager when RMAN is running Fixed in 11g Release2 and included in patchset 10.2.0.5 and 11.1.0.7 Workaround:      Disable Resource Manager. One-off patches available  Patch 6874858 Bug 16392079 -SESSIONS HANG. WAITING FOR 'RESMGR:CPU QUANTUM'           Fixed in 11.2.0.4 and 12.1.0.1 See also  Note 759503.1 Resource Manager Plan Changes Settings Every Week which might be causing higher waits on 'RESMGR:  ' events due to the changed Resource Plan. NOTE: A complete list of patches required to address this problem is maintained by the resource manager product team in Note 1339803.1 - Recommended Patches for CPU Resource Manager   REFERENCES BUG:6874858 - WESTFIELD1 - CONNECTION TIMEOUT WHEN RMAN BACKUP RUNING BUG:7510766 - RESOURCE MANAGER IS OVER THROTTLING BUG:7527260 - HIGH WAIT EVENTS ON "RESMGR:CPU QUANTUM" WHEN RESOURCE MANAGER IS ENABLED BUG:8221960 - WAITS FOR "RESMGR:CPU QUANTUM" NOTE:10326338.8 - Bug 10326338 - High "resmgr:cpu quantum" but CPU has idle time NOTE:1339803.1 - Recommended Patches for CPU Resource Manager NOTE:759503.1 - Resource Manager Plan Changes Settings Every Week