Turn resource manager off
Mladen Gogala, July 01, 2025 - 9:15 pm UTC
Don't bother checking, resource manager plan is a complex monstrosity which can be turned off easily. Most of the DBAs configure this only once and never again. The documentation is hard to read and plan directives are complex and confusing. Turn off the resource manager and the wait event will go away.
Also, make sure that you turn off concurrent statistics collection because it will not work without the resource manager.
July 09, 2025 - 6:51 am UTC
Turn off the resource manager and the wait event will go away.
and there's a good chance something else way worse might pop up, because if you are truly short on server resources, then that's a nice way to have your instance start misbehaving or crash altogether due to CPU starvation
Cpu quantum: problem or symptom
Jonas S Rosenthal, October 07, 2025 - 2:46 am UTC
While quantum cpu shows highh counts, dont assume the database or resource manager is the problem. You need to look holisticallly starting with your awr reports.
The One key metric to observe from thhe AWR report. should start with the following .
1) Disk Latency. When time to read or write exceeds 5 to 10 ms, that's something to tahe a peak at. More importantly, when it exceeds 1 SECOND, that's a CATASTROPHE. In one use case where this happened, emc was called to check their netwok on the storage array. I was.not working properly which explained the system performance. Applications were blocked from disk, java pools surged in sessions and cpu spiked. First thing to check is disk latency. If you don't, you are chasing your tail. Ill be back with more comments tomorrow.