Identify two tasks that the Database Resource Manager can perform, which the I/O Resource Manager cannot.

Identify two tasks that the Database Resource Manager can perform, which the I/O Resource
Manager cannot.

A.
Manage I/O based on the application that is connected to the database.

B.
Manage the number of parallel sessions for a query.

C.
Manage I/O and CPU between databases on the same cluster or physical database host.

D.
Terminate database sessions when certain limits have been reached.

E.
Manage the throughput of an I/O-bound application based on the service name used for the
connection.

Explanation:
IORM is similar to Oracle Database Resource Manager (DBRM) in that it provides a
means for controlling allocation of system resources. Where DBRM’s primary goals are to control
CPU resources, limit the degree of parallelism, and impose resource consumption constraints for
different types of sessions within an Oracle database, IORM’s goal is to govern I/O resource
allocations between databases on a shared storage infrastructure. When consolidating Oracle
databases on Exadata, IORM can be used to ensure that I/O is controlled between databases as
well as classifications of consumes that utilize the same ASM disk infrastructure and, as such,
provide resource control capabilities beyond what DBRM provides within a database.
/ Using the Database Resource Manager, you can:
* Guarantee certain users a minimum amount of processing resources regardless of the load on
the system and the number of users
* Distribute available processing resources by allocating percentages of CPU time to different
users and applications. In a data warehouse, a higher percentage may be given to ROLAP
(relational on-line analytical processing) applications than to batch jobs.
* Limit the degree of parallelism of any operation performed by members of a group of users
etc