Why Exadata for Oracle Databases?

Many time it comes in our mind that why we should go for Exadata, what benefits we can get if we go for Exadata so here we have given some views based on the Exadata architecture, experience and features. This is the most common question in interview.

No doubt there can be many more advantages than what we have given below as we have only given high level views.

• Exadata is high performance and high available pre-configured device.
• It consists of servers,storage networking and software in single pre-configured box which is massively scalable, secure and redundant.
• Multiple compression tiers are available on Exadata which can help customer to compress data as per business requirement to save storage space.
• Implementation time is very less compare to non-Exadata systems as it's comes as pre-configured and pre-tested.
• In case on any issue with the Exadata than we need to communicate with only single vendor which doesn't required to contact multiple vendor like non-Exadata setup so solution of issue could be done quicker.
• Only DMA (Database Machine Administrator) would be required to manage the Exadata so it can manage with lower TCO which reduce the huge cost of manageability.
• Exadata provides extreme performance for both DW and OLTP databases which is making it and ideal platform for database consolidation.

Oracle Exadata IORM

IORM is the great feature come with Exadata which gives us to control the resources for multiple databases as well as different workloads on same database . Just given overview regarding IORM.

IORM is the extension of DBRM. IORM does not directly improve efficiency of operation by reducing the amount of resources required but  I/O Resource Manager contributes to improved efficiency by ensuring that in a scenario where there is more demand for a resource than can be simultaneously supplied by the Exadata Storage Server, the most critical operations will deliver a consistent quality of service.

We can priorotize the storage I/O to the Database based on the criticality of the database. IORM deliver consistent performance quality. IORM guarantee that particular DB will get percentage of resources at any time.

When bandwidth is dividing in different workload in same database, it's called intradatabase resource management. In this case IORM does not come in the picture as whole resource utilization can be configured on compute node.

When bandwidth is dividing for different databases, it's called interdatabase IORM. In this scenario IORM need to be configured on cell level.

IORM Architecture: