Which three resources might be prioritized between competing pluggable databases when creating a multitenant container database plan…?

Which three resources might be prioritized between competing pluggable databases when

creating a multitenant container database plan (CDB plan) using Oracle Database Resource
Manager?

Which three resources might be prioritized between competing pluggable databases when

creating a multitenant container database plan (CDB plan) using Oracle Database Resource
Manager?

A.
Maximum Undo per consumer group

B.
Maximum Idle time

C.
Parallel server limit

D.
CPU

E.
Exadata I/O

F.
Local file system I/O

Explanation:



Leave a Reply 8

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


ora600

ora600

Correct answer: C,D
I have no clue why oracle thinks there are 3 correct answers! I would choose A,C,D

Dr. Oracle

Dr. Oracle

C, D is defintely correct, but I am not sure about A.

abhishek

abhishek

This question need some correction,
beucase right now as per Oracle documentation at PDB level we can only prioritize CPU and Parallel execution servers.
PFB the the referece url for the same
http://docs.oracle.com/database/121/ADMIN/cdb_dbrm.htm#ADMIN13777

But Database consumer group level we can manage all of below resource

“Resource plan directives specify how resources are allocated to resource consumer groups or subplans. Each directive can specify several different methods for allocating resources to its consumer group or subplan. The following sections summarize these resource allocation methods:

CPU
Exadata I/O
Parallel Execution Servers
Runaway Queries
Active Session Pool with Queuing
Undo Pool
Idle Time Limit

Ref :http://docs.oracle.com/database/121/ADMIN/dbrm.htm#ADMIN11851

So in question it should be only two option which are correct.

reivaj

reivaj

CDE

In a CDB with multiple PDBs, some PDBs typically are more important than others. The
Resource Manager enables you to prioritize the resource (CPU and I/O, as well as allocation of
parallel execution slaves in the context of parallel statement queuing) usage of specific PDBs.
This is done by granting different PDBs different shares of the system resources so that more
resources are allocated to the more important PDBs.
In addition, limits can be used to restrain the system resource usage of specific PDBs.
When a PDB is plugged in to a CDB and no directive is defined for it, the PDB uses the default
directive for PDBs. As the CDB DBA, you can control this default and you can also create a
specific directive for each new PDB