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 (ODA SW) across all Database Appliance hardware models. ODA SW has a support life of five years after the Last Ship Date.

Oracle recommends moving to a new system after your appliance reaches its final certified Oracle Database software release. Customers can either upgrade to a current ODA system model and continue with an on-premises ODA deployment, or transition to Oracle Base Database Cloud@Customer, which provides Oracle Database cloud services on Oracle-managed infrastructure deployed in the customer’s data center. Cloud@Customer offers a cloud operating and consumption model while allowing databases to remain on-premises to address data residency, security, latency, and application proximity requirements.

Customers that are not yet ready to purchase and migrate to a new ODA or Cloud@Customer system may continue operating eligible existing ODA hardware by running the ODA Persistiveness script. This enables Oracle Database, Oracle Grid Infrastructure, and firmware to be maintained using standard Oracle x86 procedures. However, because the operating system remains tied to the existing hardware platform, future Oracle Linux major version upgrades are not supported.

To continue getting Oracle support, you must maintain a valid Oracle Hardware Support contract (Premier Support for Systems) and Oracle Database software support contract.

The following table shows the Appliance Manager software support expiration date for each Oracle Database Appliance (ODA) hardware model. For models that have reached the expiration date, the table also identifies the last supported Appliance Manager release.

FAQs:

1. What is the ODA Persistiveness script?
The optional ODA Persistiveness script converts an Oracle Database Appliance from Appliance Manager lifecycle management to a standard x86 system after the appliance reaches its final certified Appliance Manager software release.

For supported bare metal deployments, existing databases remain in place and future management is performed using standard Oracle Linux, Oracle Grid Infrastructure, Oracle Database, and firmware maintenance procedures.

2. When should I use the optional ODA Persistiveness script?
Use the Persistiveness script after your ODA model reaches its final certified ODA software release and you want to continue operating the hardware while keeping Oracle Linux, firmware, Oracle Grid Infrastructure, and Oracle Database up to date.

3. What happens to my Oracle Database Appliance after I run the Persistiveness script?
The appliance is no longer managed by ODA software and becomes a standard x86 system.
Future administration—including firmware, Oracle Linux, Oracle Grid Infrastructure, and Oracle Database updates—is performed using standard Oracle administration methods.

4. What features or functionality do I lose after running the Persistiveness script?
ODA lifecycle management, including infrastructure and database operations using ODA software tooling, is no longer available. Administration is performed using standard Oracle management tools.

5. Can I continue using my existing databases after running the Persistiveness script?
Yes, for supported bare metal deployments. Your existing databases remain intact, and no reimaging, reinstallation, or redeployment is required.

For virtualized Oracle Database Appliance deployments, KVMs are not supported by the Persistiveness script and are permanently deleted when the script is run. Before running the script, back up all databases and other data that must be retained from the KVMs. After the script completes, the KVMs must be recreated in a supported environment and the databases restored from backup.

6. Can I continue applying Oracle Database and Grid Infrastructure Release Updates (RUs)?
Yes. After running the Persistiveness script, you can continue applying Oracle Grid Infrastructure updates, Oracle Database Release Updates (RUs), Oracle Linux updates, firmware updates, and security patches using standard Oracle procedures.

7. Can I continue using Appliance Manager (odacli) after running the Persistiveness script?
No. After running the Persistiveness script, ODA software and odacli can no longer be used to manage the appliance. Future administration and lifecycle management are performed using standard Oracle procedures and tools.

8. Will my Oracle Database Appliance continue to receive hardware support and replacement parts?
Yes. As long as you maintain an active Oracle Hardware Support contract (Premier Support for Systems), your appliance remains eligible for hardware support and replacement services. To remain eligible for hardware support, the appliance must remain in a certified hardware configuration. Customers cannot not install non-approved hardware upgrades or modifications that are not supported by Oracle.

9. Are there any limitations or unsupported configurations?
Yes. After running the Persistiveness script, your Oracle Database Appliance remains eligible for hardware support and replacement parts as long as you maintain an active Oracle Hardware Support contract (Premier Support for Systems) and the appliance remains in a certified hardware configuration. Do not install hardware upgrades or make hardware modifications that are not supported by Oracle.

10. How do I obtain and run the ODA Persistiveness script?
The ODA Persistiveness script (oda_persistiveness.pl) is available for download from My Oracle Support (MOS). A valid MOS login and Customer Support Identifier (CSI) are required to download the script.
For high availability systems:

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. After the script completes, manually restart Oracle crs/Clusterware on either node if it is not running.

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.

11. Can the Persistiveness script be reversed after it has been executed?
No. The conversion is intended to be permanent. After the appliance has transitioned to standard Oracle x86 management, ODA software lifecycle management cannot be restored.

12. Where can I get help or more information?
For technical assistance, open a Service Request (SR) through My Oracle Support.
For information about Oracle Hardware Support, Oracle Database support lifecycles, and Oracle Lifetime Support policies, refer to the Oracle Lifetime Support documentation and the Oracle support resources available through My Oracle Support. Here are some links:

• Oracle Technology Products – Lifetime Support Policy
• Lifetime support policy: coverage for Oracle open source service offerings
• Oracle Open Source Support Policies
• Oracle Hardware and Systems Support Policies

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. 

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.