Why Oracle Database Appliance (ODA)
I recently attended a deep dive on the Oracle Database Appliance (ODA) and let me tell you, there is a lot to love with this product. Briefly, it’s a single 4-RU appliance that contains a pair of servers and 12 TB (raw) of SAS disk storage. The servers are clustered using internal redundant 1 GbE interconnects, and support both 1 GbE and 10 GbE external networking connectivity. Hence, this will easily fit into both 1 & 10 GbE environments. Each server, running Oracle Linux, comes with a pair of 6-core Intel Xeon CPUs and 96 GB of RAM.
Four 73 Gb Solid-State disks (SSDs) provide extremely fast access to the Oracle redo logs. Also, this appliance supports both Oracle RAC and Oracle Rac One Node for “active-active” or “active-passive” failover of the database. As a matter of fact, the only issue I see with the ODA, is that (currently) you MUST triple mirror and hence get only 4 TB of usable storage. Supporting both OLTP and DW applications, ODA could fit in a number of deployments. Every deployment? Probably not, although IT IS A very versatile tool in our toolbox.
Bluenog specializes in building applications based on the Oracle Middleware, SOA, and Identity Management stacks. Most of these components do have minor database needs by themselves, but If we were building an application that had large storage needs of its own, then it may be considered. Another possibility would be a situation where the data needed to remain isolated for, say, compliance reasons. In this situation, it may not be acceptable to keep the data on the same large storage array used by other facets of the company.
We also have a very active Engineered Systems practice that is currently involved in a number of Exadata and Exalogic systems; also game changing products. In a situation where the customer didn’t need the capacity of an Exadata, ODA could fit very nicely.