ORACLE isn’t a one-person job, as the database interfaces with hundreds of capabilities and components. Data architects, database administrators (DBAs), storage managers, plus a host of other business personnel must work coordinate in order to appropriately configure storage for ORACLE and appropriately tune the storage for optimal performance. I’ve included several tips to be able to simplify system configuration and performance tuning on your storage system.
Configuring the Big Four
You can find four main hardware components to consider when creating or fine-tuning an Oracle hardware infrastructure. Architects should ensure a balanced design, as the entire system is only as powerful as the weakest link.
CPU Memory Data Storage Network
Although frequently an improvement in one or many of the above components may possibly generate an improvement in performance, there are limits to that improvement based on which variable might be developing a efficiency constraint.
Carefully identifying the difficulty component will make it less complicated and much more cost-effective to alleviate any efficiency constraints that may be occurring. Any performance increases that result from adding hardware ought to be regarded as short-term relief, as increased application use is most likely to trigger the very same troubles in the near future.
Talk with a storage expert to establish what method is most likely to scale most successfully for your environment when sizing or deploying a new system to support your Oracle databases.
Symptoms and Troubles
Slow Physical I/O – This results when disks have been configured improperly or too few resources have been allocated to support the database.
Excessive CPU Usage – Excessive CPU usage means there is certainly small to no idle CPU on the storage system. This can occur when a system has not been sized adequately as a result of inability of the CPU to scale and meet demand.
Outages – This can occur when appropriate redundancy has not been built into the system to be able to account for failures
Typically, the symptoms are indication of an underlying issue in the hardware, poorly configured solutions, or untuned SQL statements.
Hardware and I/O Considerations
I/O performance is a key component when designing Oracle systems. When I/O workloads are particularly intensive, the underlying I/O or storage program should be designed to meet these requirements. Under-sizing a solution can lead to lost time and wasted resources for your company. These five guidelines can help you make certain that your system is properly built to support your databases for the whole life-cycle of the application.
Configure I/O for Bandwidth Before Capacity
Storage configurations ought to be assembled based on I/O bandwidth, and not merely on their overall storage capacity. The capacity of every disk drive is growing a lot quicker than their I/O throughput rates, developing a scenario where a modest quantity of disks can hold a large information volume. Even so, these disks can’t deal with the throughput of smaller disks. As an example, spreading data over numerous 146GB or 73GB drives will result in better performance than a single 600GB disk.
Stripe as “Far and Wide” As Feasible
Oracle recommends utilizing multiple disks and channels across database objects. This may be accomplished by striping datafiles of the Oracle databases bring deployed.
Use Redundancy
Disk redundancy is a requirement to defend against hardware failure. A key consideration is that often a balance ought to be struck between redundancy and performance. RAID 5 may possibly be much less expensive than RAID 10, however it may possibly not perform too. If cost constraints are an problem, a storage consultant can assist you to decrease the cost of the remedy and still meet your necessary performance levels.
Test The Program Prior to Creating A Database
Examine I/O and tune the system just before the database is developed. When the file is created, reconfiguring the files becomes a lot a lot more difficult. Greater collaboration across system resources makes this a troubling effort. It is crucial to keep in mind that I/O bandwidth really should be tested to validate that expected I/O levels are becoming accomplished.
Program for Growth
It is imperative to plan for future growth of an Oracle database. The key would be to be able to grow and not compromise I/O bandwidth. Not properly planning for growth will eventually trigger over-utilization of resources and efficiency issues.
Note: You can’t simply add disks to an existing system and add a brand new database table across new disks. Correctly sizing the disk program the first time prevents complicated upgrades and migration in order to grow an I/O system inside the array.
Bottleneck Elimination
The purpose of tuning would be to lessen resource consumption or lessen time for an operation to be completed. In general, performance issues result when a resource is over-used. This created a bottleneck in the method. Contention is actually a symptom that will frequently be fixed by generating the adjustments below:
Modifications in the way the application is being utilized Changes in your Oracle database Changes in hardware configurations
Get It Right The first Time
Consider these requirements when designing a storage program and SAN to support your Oracle databases:
Storage – Minimum disk capacity and spindle count. Keep in mind that a lot more spindles yields greater efficiency. Availability – Is this a 24/7 system or will it only be utilized throughout business hours? 24/7 utilization needs correct engineering that may deal with maintenance with no outages. Efficiency – I/O throughput and application response times will decide the needed configuration
If you are in the market for EMC Storage or IBM Storage, we’re the top seller for all your technology storage needs. You will save thousands on excellent new and refurbished hardware equipment.