Oracle Database 18c (18.2) Now Available on Oracle Database Appliance

Tammy Bednar
Senior Director of Product Management

I am happy to announce the availability of Oracle Database 18c on Oracle Database Appliance.   This Database Appliance release marks a new and exciting time, giving you the opportunity to start testing and using the new Oracle Database 18c functionality and improvements with your applications.

For Oracle Database Appliance customers, the Hybrid Columnar Compression (HCC) functionality will be made available starting with the Database 18c release.  The HCC feature will provide the ability to recognize storage savings achieved from compression.  For more information on HCC, please take a look at the Oracle Documentation.

For more information on Oracle Database 18c features,

Read the announcement blog.
Read the white paper: Introducing Oracle Database 18c.
Read the documentation.

How can you download and use the Oracle Database 18c release on ODA?

The Oracle Database Appliance 18.2 release is a special parallel release that you can use to try Oracle Database 18.2. ODA 18.2 is not part of the ODA patch cycle.  If you are looking to run database versions of or or, then this release is not for you.  Please refer to this ODA Blog Post on the ODA software stack on planned patch updates.   https://blogs.oracle.com/oda/the-two-software-stacks-of-oracle-database-appliance

Oracle Database Appliance 18.2 supports Oracle Database Appliance models X7-2-HA (bare metal), X7-2S/M, X6-2-HA (bare metal), X6-2S/X6-2M/X6-2L and X5-2. You must re-image your ODA and deploy the ODA 18.2 patches to access the Oracle Database Appliance 18c software. The 18.2 release only supports provisioning 18.2 databases.  For more information, please take a look the Oracle Database Appliance 18.2 documentation at Oracle Database Appliance 18.2 

The 18.2 release is available in MOS to download.


Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.