Consolidation is a key enabler for Oracle database deployments on both public and private clouds. Consolidation reduces the overall IT costs by optimizing the operational and capital expenses. In addition, it enhances the effective utilization of cloud resources. The Exadata database machine has been optimized to run schemas and databases with mixed workloads together, making it the best platform for consolidation.
Organizations follow different approaches to consolidate database instances. Some of the prominent approaches of consolidation are virtualization, schema based consolidation and database aggregation on a single high end physical server. Oracle Database 12c introduces Multitenant Architecture to allow secure consolidation of databases on cloud and achieve benefits like tenant isolation, manage many-as-one capability and enhanced customer satisfaction.
For effective database consolidation, Exadata makes use of Oracle resource management (database resource management, network resource management and I/O resource management). The Exadata IORM enhances the stability of mission critical applications and ensures availability of all databases which share the server resources. The I/O resource plan provides the framework for queuing the low-priority requests while issuing high-priority requests. This post will focus on configuring, enabling and monitoring IORM plans on Exadata database machines.
Oracle Database Resource Manager
On a database server, the resources are allocated by the operating system, which may be inappropriate and inefficient in maintaining database health. The server stability and database instance is impacted by the high CPU load, thus resulting in sub-optimal performance of the database. Oracle Database Resource Manager, first introduced in Oracle Database 8i, can help you by governing the allocation of resources to the database instance and assuring efficient utilization of CPU resources on the server. It is a database module which allocates the resources to a resource consumer group as per a set of plan directives in a fair way. A resource consumer group comprises of database sessions with “like” resource requirements.
A resource plan can manage the allocation of CPU, disk I/Os and parallel servers among schemas in a single database or multiple databases in a consolidated environment. An intra-database plan can be created to manage allocation across multiple schemas or services within a single database. On an Exadata database machine, the disk I/Os can be managed across multiple databases using IO Resource Manager (IORM) or inter-database plan. The Oracle Database Resource Manager is a feature of Oracle Database Enterprise Edition. However, starting with Oracle Database 11g, it can also be used in Standard Edition to manage maintenance tasks through a default maintenance plan.
This post focuses on configuration of IORM plans on the Exadata database machine. In the post, we shall discuss how to manage disk I/Os, manage flash usage, manage standby database using IORM.
Read the complete post at Community.Oracle here – https://community.oracle.com/docs/DOC-998939