Which two steps are needed to set up instance caging on an Exadata system? (Choose two.)
A.
Set the CPU_COUNT parameter to the maximum number of CPUs that the database instance should
utilize at any time.
B.
Enable a resource plan to manage the CPUs.
C.
Specify the optimization objective as low_latency or high__throughput.
D.
Set PGA_AGGREGATE_LIMIT to an acceptable level for the intended instances.
E.
Change the initialization parameter THREADED_EXECUTION to TRUE and restart the instance.
Explanation:
http://www.oracle.com/technetwork/database/performance/instance-caging-wp-166854.pdf
Right ?
YES this is correct Colu.
Like Igor says, It’s right.
Take a look,
1. Enable the Oracle Database Resource Manager by assigning a resource plan to
RESOURCE_MANAGER_PLAN initialization parameter. The resource plan must have CPU
directives to enable instance caging. See Oracle Database Administration’s Guide 11g Release 2
“Enabling Oracle Database Resource Manager and Switching Plans” for instructions. If you are
not planning on managing workloads within a database, you can simply set
RESOURCE_MANAGER_PLAN to “DEFAULT_PLAN”.
SQL> ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = ‘DEFAULT_PLAN’
SID=’*’ SCOPE=’BOTH’;
2. Set the CPU_COUNT initialization parameter to the maximum number of CPUs the instance
should use at any time. By default, CPU_COUNT is set to the total number of CPUs on the
server. For hyper-threaded CPUs, CPU_COUNT includes CPU threads. CPU_COUNT is a
dynamic parameter, so its value can be altered at any time but it is best set at instance startup
because the CPU_COUNT parameter influences other Oracle parameters and internal structures
(for example, PARALLEL_MAX_SERVERS, buffer cache, and latch structure allocations).
http://www.oracle.com/technetwork/database/availability/exadata-consolidation-522500.pdf