########################################################### ## How to implement Oracle Instance Caging ###########################################################
Instance Caging allows to dynamically limit the amount of CPUs used by each database instance. This option is specifically thought for shared environments where the database administrator has to guarantee resources to all the instances running on the same hardware.
-- Enable Resource Manager:
ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = 'REAL_TIME_PLAN';
--or
ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = 'FORCE:REAL_TIME_PLAN';
FORCE option prevents that the scheduler window activates a different plan during the job execution.
########################################################### ## Instance Caging Test ########################################################### Hardware SUN 8 Cores 64 Threads One test database capped to 16 CPU - 25% of total hardware capacity.
ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = 'default_plan'; ALTER SYSTEM SET cpu_count=16 scope=both sid='*';
The load generator opens 70 sessions producing intencive CPU activity, which as shown by the reports below do not exceed the 25% od the total server capacity (%Usr column).