Re: Resource Manager

You can manually set the cpu_count in order to cage the cpu usage of the database. This may be fairly new, but it is documented. Resource manager must be enabled to do this.

Sent from my iPad

> On Apr 14, 2020, at 11:58, Chris Taylor <christopherdtaylor1994_at_gmail.com> wrote:
> 
> 
> As far as I know (as a heavy user of resource manager) , there is no correlation between CPU_COUNT and resource manager ?
> 
> If CPU_COUNT isn't being set dynamically by the instance, then it sounds like someone set it manually to null (which I didn't think was possible).
> 
> So double check gv$parameter where name = 'cpu_count' to see if its set, and has been modified.  If it's set and is modified you can reset it to default but I think will require a db bounce for it to autopopulate.  You can also set it manually as you would expect to to the number of cpus shown by the OS , but don't set it higher than the number of CPUs shown by the OS.
> 
> As far as "resource_manager_plans" that's another parameter you can check in gv$parameter to see what it's set to.
> 
> You can force a plan if you want using "FORCE:" key word such as:
> 
> alter system set resource_manager_plan="FORCE:<some plan name>" scope=both sid='*' ;
> 
> That will prevent it from changing.
> 
> DBA_SCHEDULER_WINDOWS will automatically set the plan if the scheduler window has:
> a.) a resource plan specified AND
> b.) the window has the allow_scheduler_plan_switches set to TRUE
> 
> Chris
> 

--
http://www.freelists.org/webpage/oracle-l