What is Oracle Database Appliance?

Oracle Database Appliance is an “always on” database system. It does not have to go down if a component fails. Component failures are accounted for and the configuration is built with redundancy and single point of failures in mind. Further, it is a very simple system to deploy and operate.

If you are familiar with Oracle technologies, then technically, the best way to look at the Oracle Database Appliance may be to think of it as a two node Oracle Linux RAC cluster in a single box with shared storage and networking all included in the box. It is built and configured with redundancy to achieve continuous availability in the event of component failures. It addresses all single points of failures within the system.

ü Pre-built

ü Pre-configured

ü Pre-tested

ü Pre-validated

ü Pre-tuned

The current software stack (as of April, 2012) consists of Oracle Linux 5.8 (with the UEK kernel), Oracle Grid Infrastructure, and Oracle Database On your Oracle Database Appliance, you can run Oracle RAC databases, Oracle Single Instance databases, or Oracle RAC One (active – passive) databases, or a combination of these.

Oracle Database Appliance is extremely simple to deploy. When you receive your appliance unit, you simply put the appliance in a computer rack, (or you can place it on a table, or in a closet), then you plug in the power and network connections to the Database Appliance and power on the Oracle Database Appliance. You then input the information for your configuration (system names, database names, database size, etc.) and for all practical purposes you just issue a single command to complete the deployment of your Oracle Database Appliance. That command is “oakcli deploy” that you issue from Linux system prompt. More on that will be covered later. The command initiates the entire process of setting up the OS, installing Oracle software, creating the initial database, and optionally setting up a cloud file system volume (a shared file system), configuring Oracle Auto Service Request, etc. as you watch the progress on your screen.

The multiple weeks’ worth of effort previously required in configuring an HA database is no longer necessary! The actual deployment process in fact takes less than one hour. And at the end of that one hour you have a fully functional cluster and a fully usable database available for your application to use.

Customers typically complete their deployments on the day they open the box and put the appliance in the rack. What is really interesting is the side benefit of this ease of use which results in lower chances of errors in configuration. The risks and uncertainties involved in setting up the HA system have virtually disappeared. And that means a lot for users. Now they can go ahead and buy an Oracle Database Appliance knowing that they can have a fully functional highly available database system on the day that it arrives!


Follow @OracleODA, https://twitter.com/OracleODA, on Twitter for ODA news, announcements and Oracle Open World session information, agendas and updates.

Posted by guest on September 07, 2012 at 07:56 AM PDT #

hello, i need change all ip addresses for my ODA, how can i do that?

Posted by guest on October 01, 2013 at 07:43 AM PDT #


Thanks for your question. Sometimes changing the IP addresses on Oracle Database Appliance is required for moving an Oracle Database Apliance across different sites and networks for POCs, testing etc. In other cases, you may be moving your pre-deployed, functioning production system across data centers, etc. The latter is rare but possible.

If this is a production system then get in touch with Oracle Support. My Oracle Support note 1504734.1 provides instructions on how to change the IP addresses on Oracle Database Appliance. Please make sure you have good backups before you do the change.

If this is a temporary environment that can be simply wiped out then doing a cleanup and re-deployment with the new IP addresses may be an easy approach to deployment a new set of IP addresses, for such systems. The cleanup for such temporary systems can be done using the cleanupDeploy.pl script (look inside the /opt/oracle/oak/onecmd/ directory).

Please remember that the cleanup and re-deployment will wipe out all data on your Oracle Database Appliance. So, exercise extreme caution before considering this option.

Thanks, Ravi Sharma

Posted by Ravi Sharma on October 01, 2013 at 09:01 AM PDT #

hi. how do we find out whether it is an x4-2 or the other model?

Posted by man on February 26, 2014 at 12:02 AM PST #

You can use the "oakcli show env_hw" command from either node to identify whether your Oracle Database Appliance unit is V1 hardware, V2 (X3-2) hardware, or V3 (X4-2) hardware.

Please see below an example from different hardware environments.

These outputs are from a virtualized platform implementation therefore you see "VM-ODA_BASE" prefixed to the output. In a bare metal (non-virualized) environment you will see "BM" prefix.

[root@oda1n1 ~]# oakcli show env_hw

[root@oda2n1 ~]# oakcli show env_hw

[root@oda3n1 ~]# oakcli show env_hw

Hope this helps.
Regards, Ravi

Posted by Ravi Sharma on February 26, 2014 at 07:56 AM PST #

Hello, What is the End of life support for ODA hardware? While I understand Oracle has lifetime support for ODA software. Is that a correct understanding.


Posted by guest on December 01, 2015 at 12:13 PM PST #

Post a Comment:
  • HTML Syntax: NOT allowed

The Oracle Database Appliance saves time and money by simplifying deployment, maintenance, and support of high-availability database solutions. This blog is dedicated to sharing updates about the Oracle Database Appliance from your product team.


« July 2016