Oracle Database Appliance launched its first model, V1, in Oct 2011.  Since then, additional hardware models have been released with the ability to run the same version of the Database Appliance Manager software across all Database Appliance hardware models.

Oracle Database Appliance Manager software has a support life of five years after the Last Ship Date.

The following models have reached the five-year expiration date for Appliance Manager software certification:

  • Oracle Database Appliance Manager software certification (e.g. odacli and oakcli) for ODA X7-2 ended with the 19.27 release.
  • Oracle Database Appliance Manager software certification (e.g. odacli and oakcli) for ODA X6-2 ended with the 19.19 release. 
  • Oracle Database Appliance Manager software certification (e.g. odacli and oakcli) for ODA X5-2 ended with the 19.18 release. 
  • Oracle Database Appliance Manager software certification (e.g. odacli and oakcli) for ODA X4-2 ended with the 18.8 release. 
  • Oracle Database Appliance Manager software certification (e.g. odacli and oakcli) for ODA X3-2 ended with the 18.5 release. 
  • Oracle Database Appliance Manager software certification (e.g. oakcli) for ODA V1 ended with the 12.2.1.4 release. 
ODA Hardware Model First Ship Date Last Ship Date Appliance Manager Software Support
ODA V1 Oct 2011 May 2013 July 2018 – Last supported Appliance Manager release:  12.2.1.4
ODA X3-2 Mar 2013 Feb 2014 Mar 2019 – Last supported Appliance Manager release:  18.5
ODA X4-2 Dec 2013 May 2015 Apr 2020 – Last supported Appliance Manager release:  18.8
ODA X5-2 Feb 2015 Feb 2018 Feb 2023 – Last supported Appliance Manager release: 19.18
ODA X6-2 (all models) Jun 2016 Feb 2018 May 2023 – last supported Appliance Manager release: 19.19
ODA X7-2 (all models) Oct 2017 May 2020 Jun 2025 – last supported Appliance Manager release: 19.27
ODA X8-2 (all models) Sep 2019 Aug 2022 Aug 2027
ODA X9-2 (all models) June 2022 Nov 2024 Nov 2029
ODA X10 (all models) Sept 2023 May 2025 May 2030
ODA X11 (all models) Jan 2025 TBD TBD

 

 

 

 

 

 

 

 

 

FAQs:

Q: Can I continue to use my Database Appliance beyond the Appliance Manager last support date?
A:  Yes -You will need a valid Oracle hardware support contract and a valid Database software support contract in place.

Q: How can I update my databases after the Appliance Manager software last support date?
A: 
ODA bare-metal customers who want to update their databases, must run the ODA-Persistiveness script to convert their ODA into a generic x86 system.  Customers do not need to re-image or re-deploy their databases. After the ODA-Persistiveness script is run, customers can use standard x86 administrative methods to update firmware, the Linux Operation System (OS), and databases.
Customers running ODA virtualized systems who want to update their databases after the Application Manager last support date, must first back up their databases, and install (your choice) in bare metal or Oracle KVM, and re-deploy their databases with Oracle KVM.  (Please see the Oracle Virtualization documentation for more information at https://docs.oracle.com/en/virtualization/).

Q: Where can I find the correct ODA-Persistiveness scripts?
A: :
The ODA-Persistiveness script for ODA V1, ODA X3-2, ODA X4-2, ODA X5-2, ODA X6-2, ODA X7-2 can be downloaded here: oda_persistiveness.pl, and make sure to click on the drop down menu to select the correct release. Requires login and CSI to download.

Q: How do I use the ODA-Persistiveness scripts?
A:

  1. Run the script from the 1st node (Node 0).
  2. After the script has successfully finished running on the 1st node (Node 0) , run the script on the 2nd node (Node 1).
  3. Manually restart the crs/clusterware for both nodes if crs/clusterware is down.

NOTE: If the script had previously successfully completed on the 1st node (Node 0) and rebooted, it is only necessary to run the script on the 2nd node (Node 1). This will stop the clusterware on both nodes, and you will need to manually start clusterware for the 1st node after rebooting the 2nd node.

Q:  Are there any limitations with the persistiveness script?
A: 
Yes – the persistiveness script does not support ODA with DB SYSTEM, Application KVM, IDM & DPR. The ODA persistiveness script does not support DBSystem or Application KVM. Please be advised to take a full backup of any Databases in DBSystem/KVM guests, as they will be permanently deleted once the ODA system is repurposed using the persistiveness script. For any assistance in taking a backup, reach out to the support team.

Q: Where can I find more information about Oracle x86 hardware and database support?
A:
Oracle hardware and database software will continue to be supported as long as the support contract is in effect. Please see the details below:
https://www.oracle.com/support/lifetime-support/index.html
http://www.oracle.com/us/support/library/057419.pdf

Q: What if I need a security patch that becomes available after the Appliance Manager last support date? 
A:
  The best practice is to keep your system and software up-to-date.  It is recommended that you run the ODA-Persistiveness script and maintain the hardware as a generic x86 system. 

Q:  Can I apply future Database Appliance patches after the last support date?
A: Yes
 –  However, understand we do not test new versions of the Database Appliance Manager software on models that are beyond the last support date listed.  If you would like to continue to use the hardware platform, it is recommended to run the ODA-Persistiveness script and maintain it as a generic x86 system.

Q:  Could I just apply the GRID and Database PSU/BP/RU to the ODA after the Appliance Manager last support date?    
A:
  Only after the ODA-Persistiveness script has been run on your Database Appliance.  Oracle Grid Infrastructure and Database software schedule and support information are maintained independently of the Database Appliance Patch releases. 

Q:  If I run the ODA-Persistiveness script, is the hardware supported beyond the Appliance Manager last support date?
A: 
Yes – As long as your hardware support contract is in effect, hardware replacements are supported. Please consult Oracle Support to understand any hardware specific issues.