Which statement is true about instance caging setup?

Which statement is true about instance caging setup?

Which statement is true about instance caging setup?

A.
Instance caging is the right approach to make sure that database instances are not stealing
memory from each other.

B.
The CPU Resource Manager and IORM need to be enabled to make instance caging to work
as expected.

C.
Database instances need to be restarted to make changes to cpu_count effective.

D.
For a system with 16 threads, the sum of cpu_count for all databases should not be higher than
32 to prevent oversubscribing

E.
The init.org parameter resource_manager_plan should be set.

Explanation:
* In 11.2G there is new option called “Instance Caging” which enables to limit
number of CPUs which can be seen/used by a database.
* Enabling Instance Caging
1. Manually set dynamic parameter cpu_count on instance level. As default this parameter is set to
maximum number of cpu available on a hosts.
alter system set cpu_count=2;
2. Enable any resource manager plan that manages CPU. Most easy is to turn on defaultOracle
plan DEFAULT_PLAN.
alter system set resource_manager_plan=DEFAULT_PLAN;
* Provisioning CPU
There are generally 2 ways to distribute your CPU between databases
Partitioning – sum of all CPUs assigned to all your databases equals number of CPUs on a host.
Databases don’t interfere with each other.
Over-provisioning – sum of all CPUs assigned to all your databases is higher that number of CPUs
on a host. Databases can impact on each other performance.



Leave a Reply 2

Your email address will not be published. Required fields are marked *


Matt

Matt

Answer is E

* Enabling Instance Caging
1. Manually set dynamic parameter cpu_count on instance level. As default this parameter is set to maximum number of cpu available on a hosts.

alter system set cpu_count=2;

2. Enable any resource manager plan that manages CPU. Most easy is to turn on defaultOracle plan DEFAULT_PLAN.

alter system set resource_manager_plan=DEFAULT_PLAN;