Which three types of classification can you use to prioritize I/O requests with IORM?

Question

Options

• ABased on Database Manager Resource Groups
• BBased on an Intradatabase Plan
• CBased on a Category Plan
• DBased on the priority of the background process

• A
  80% (32)
• D
  20% (8)

Explanation

Exadata implements Smart I/O Resource management at three levels: * Transaction Level Ensures higher priority transactions get better throughput *Database Level Ensures each database gets fair share of disk bandwidth *Usage Category Level Ensures interactive users are not slowed by reporting or batch Note: IORM = I/O Resource manager The DBRM and I/O resource management capabilities of Exadata storage can prevent one class of work, or one database, from monopolizing disk resources and bandwidth and ensures user defined SLAs are met when using Exadata storage. The DBRM enables the coordination and prioritization of I/O bandwidth consumed between databases, and between different users and classes of work. By tightly integrating the database with the storage environment, Exadata is aware of what types of work and how much I/O bandwidth is consumed. Users can therefore have the Exadata system identify various types of workloads, assign priority to these workloads, and ensure the most critical workloads get priority. In data warehousing, or mixed workload environments, you may want to ensure different users and tasks within a database are allocated the correct relative amount of I/O resources. For example you may want to allocate 70% of I/O resources to interactive users on the system and 30% of I/O resources to batch reporting jobs. This is simple to enforce using the DBRM and I/O resource management capabilities of Exadata storage.

No community discussion yet for this question.