I've never heard about this expression "instance caging" until I came across this topic. So, I made a quickly search in the official documentation and it was a single page to explain everything. Fast to learn.
"Instance caging is a method that uses an initialization parameter to limit the number of CPUs that an instance can use simultaneously."
To enable it you must:
- Enable Resource manager.
- Set the CPU_COINT parameter.
If you have more than one instance in the same server in you exam environment and is requested to partition your CPUs by instance, this is the way to do that.
Path to Documentation:
Administrator's Guide -> Managing Multiple Database Instances on a Single Server
Click here to go back to the Main OCM 11g Preparation page.
Have you enjoyed? Please leave a comment or give a 👍!
1 comments
Remember of situations when you omit setting up the MGMT_PX directive's attribute and go for MAX_UTILIZATION_LIMIT. There is a difference in allocating CPU resources. You get 'per CPU count' instead of 'per CPU %'
From Doc:
If you enable instance caging and set a maximum utilization limit in your resource plan, then the absolute limit is computed as a percentage of the allocated CPU resources.