Oracle Database Appliance

Oracle Corporation introduced the Oracle Database Appliance in September 2011 as a member of Oracle's family of engineered systems[1] (a group of combined hardware-and-software systems designed to provide a specific function — in this case, that of a database server). An ODA consists of a single-box device that contains the hardware, networking, storage and software needed to build a highly-available two-node clustered database server.[2]

History

Oracle Corporation introduced its first engineered database system, Oracle Exadata, in 2008. In 2011 it announced the Oracle Database Appliance. Smaller than Oracle Exadata, the Oracle Database Appliance contains less storage, memory and CPUs, and sells at a lower price-point.[3][4] According to industry analysts, Oracle expects the Oracle Database Appliance to fill the gap in its product line beneath Oracle Exadata, targeting mid-market customers.[5]

The platform proved very popular with DBAs, with enough support to launch a book about the systems.[6]

Features

The Oracle Database Appliance supports more than database systems. Starting in release 2.5 (ODAV1) and 2.5.5 (ODA V2 X3-2), the appliance can be deployed using Oracle VM. This can allow an administrator to install not only the database, but also the application tier.[7]

The Oracle Database Appliance also offers a pay-as-you-grow model for Oracle licenses. This allows you to only license the CPU count you need and not the entire capacity of the appliance. When virtualized this is supported for both the database and the application tier.

When the Oracle Database Appliance is connected to a ZS3 storage array, the DBA can leverage Hybrid Columnar Compression for data stored on the ZS3 array. This can enable not only tiered storage but also compression ratios exceeding 20x.

Hardware

The first generation of the Oracle Database Appliance (ODA V1) is a two-node cluster in a single rack-mounted chassis. Inside the chassis are two servers, configured in a cluster, with shared storage. Each server contains two six-core processors, for a total of 12 cores per server. Each server also contains 96GB memory, six 1Gbit NICs, and two 10Gbit NICs. NICs are configured in an active/passive HA (bonding) configuration. Inside the appliance holds 4 x 73GB of shared SSD storage and 20 x 600GB of shared hard disk storage. The appliance contains redundant power supplies and cooling fans. Storage is configured at deploy time for either double mirroring (giving an overall capacity of 6TB data), or triple mirroring (yielding a capacity of 4TB data).[8]

Following generations of the Oracle Database Appliance moved to a more flexible platform, utilizing Oracle X3-2 and X4-2 x86 servers and one or two SAS storage trays. Each compute node of the latest X4-based configuration includes 4 10GBaseT network ports, two 12-core Intel Xeon E5-2697 v2 processors, 256G ram and options 10gbe fiber connectivity. The system also can support up to two storage trays, each with 20 900G drives, and four 200G SSDs. This allows for 36T of raw disk space and for another 1.6T of raw SSDs. Single- and double-mirroring of disks is supported, for up to 18T of local data storage.[9]

Software

The Oracle Database Appliance runs Oracle Linux, Oracle Grid Infrastructure for cluster- and storage-management, and a choice of Oracle Enterprise Edition, Oracle Real Application Clusters (RAC) One Node, or Oracle RAC. These latter two database products leverage the clustered nature of the hardware to provide database-service failover in the event of a failure. Oracle Corporation also provides Oracle Clusterware for high-availability monitoring and cluster membership, and Oracle Automatic Storage Management (ASM) for storage- and disk-management.[10]

Oracle Appliance Kit (OAK) software offers a built-in management interface.[11]

Administration

Oracle provides a deployment tool called the appliance manager to simplify deployment and make it less time-consuming.[12] The vendor also provides special patch bundles for the database appliance, consisting of patches for firmware, the Linux OS, clustering, storage management, and database which have been tested for compatibility.[2]

Licensing

Customers can choose to license only a subset of the processor cores in the Oracle Database Appliance. This is done by disabling unnecessary processor cores in the BIOS, using a special interface. Cores can be enabled at a later time, allowing customers to increase the capacity of the appliance if required.[13]

Criticism

The Oracle Database Appliance is a fixed configuration as described above. Customers cannot cluster multiple appliances together to create a larger cluster (beyond 2 servers), nor can they expand the internal disk storage of the system beyond the two storage trays. However, if a customer runs out of storage space, they can extend their storage to dNFS-attached storage.[14] Currently, when leveraging an Oracle ZS3 array, the storage limit is approximately 3.5PB.

gollark: So are you rewriting Gibsonalloc™?
gollark: It's performant and doesn't experience this.
gollark: Why aren't you using osmarksmalloc?
gollark: How is progress on HellobOiS?
gollark: ++delete pointers

References
  1. Curtis, Bobby; Velikanov, Yury; Benner, Erik; Arshad, Fuad; Elsins, Maris; Sharman, Pete; Gallagher, Matt (2014). "9: Business Values for the ODA". Practical Oracle Database Appliance. Expert's voice in Oracle. Apress. p. 160. ISBN 9781430262657. Retrieved January 19, 2017. ODAs will maintain their place within the Oracle engineered system product lineup for the foreseeable future.
  2. "Oracle Database Appliance White Paper" (PDF). Oracle. Archived from the original (PDF) on April 13, 2013. Retrieved December 27, 2012.
  3. "Oracle Engineered Systems Price List--December 4, 2012" (PDF). Retrieved December 27, 2012.
  4. Fielding, Marc. "Comparing Oracle Database Appliance and Oracle Exadata". Pythian. Retrieved December 27, 2012.
  5. Jennings, Tim. "Oracle Applies for Database Simplicity" (PDF). Ovum. Retrieved January 12, 2013.
  6. Arshad,Benner, Curtis,Elsins, Gallagher, Sharman, Velikanov. "Practical Oracle Appliance". Apress. Retrieved June 6, 2014.CS1 maint: multiple names: authors list (link)
  7. Arshad, Fuad. "Deploying a Virtualized Oracle Appliance". fuadarshad.com. Retrieved June 6, 2014.
  8. "Oracle Database Appliance Data Sheet" (PDF). Oracle. Retrieved December 27, 2012.
  9. "Oracle Database Appliance X4-2 Datasheet" (PDF). Oracle. Retrieved June 15, 2014.
  10. Baird, Cathy. "Oracle High Availability and Best Practices". Oracle. Retrieved December 27, 2012.
  11. Curtis, Bobby; Velikanov, Yury; Benner, Erik; Arshad, Fuad; Elsins, Maris; Sharman, Pete; Gallagher, Matt (2014). "2: Integrated Lights Out Management". Practical Oracle Database Appliance. Expert's voice in Oracle. Apress. p. 13. ISBN 9781430262657. Retrieved July 28, 2017. The Oracle Database Appliance (ODA) is a bundle of two server nodes that include storage and embedded cluster networking. Each server node has an Integrated Lights Out Manager (ILOM) interface that is used for management and maintenance tasks. [...] The Oracle Appliance Kit (OAK), also known as the Oracle Appliance Manager, is the software that manages installation and patching, and in some cases, the gathering of diagnostic information and integration of the ILOM with ASR.
  12. Moltzen, Edward. "Oracle Database Appliance: Perfect Time for Sun/Oracle Offspring". CRN.com. Retrieved December 27, 2012.
  13. Walsh, Larry. "Oracle Goes Small with Database Appliance". Channelnomics. Retrieved December 27, 2012.
  14. "Oracle Database Appliance Frequently Asked Questions" (PDF). Oracle. Retrieved January 12, 2013.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.