Shared ORACLE_HOME with Gen 2 Exadata Cloud at Customer: Consolidate More, Administer Less
Back in Sept 2019, we introduced Gen 2 Exadata Cloud at Customer (Gen 2 ExaCC for short) and explained the initial release features in this blog. With the initial release, every database created on ExaCC was automatically created in its own home. There was no way to use the same home to add more databases. We are now introducing a new feature called Shared ORACLE_HOME. Shared ORACLE_HOME allows you to create multiple databases in a single ORACLE_HOME. In this post, I will explain how this new functionality works — and how to get the most out of it.
First, we are introducing a new resource called ORACLE_HOME. When you create a new ORACLE_HOME, you specify which Oracle Database version you want to use to create it. Every database subsequently created within this home will be of the same version. (see Screen 1,2 and 3). Alternatively, when you create a new database, you specify a new ORACLE_HOME you want the database to be created in. The database will be created with the version you specified and the database will reside in the ORACLE_HOME you specified. (Screen 4)
Sharing ORACLE_HOME for multiple databases allows you to consolidate more databases on your ExaCC. It is Oracle MAA best practice to use as few ORACLE_HOMEs as possible to keep maintenance and administration to minimum. For example, when you patch an ORACLE_HOME that is shared between multiple databases, all databases in the home get patched. Another big reason to use Shared ORACLE_HOME is to optimize the finite local space that is available to each compute node. Just like the old days, let’s say you have five databases, each of version 18.104.22.168, 18c (18.0.0.00) and 19c (22.214.171.124.0). In an ideal world, you would create three ORACLE_HOMEs, one for each of the three versions, and place all databases of the same version in their respective home. The Shared ORACLE_HOME feature on Exadata Cloud at Customer Gen 2 allows you to do exactly that — and it is supported from both GUI as well as command-line.
All of the associated functionality you’d expect, like viewing all of the homes in a VM Cluster, viewing the databases in any home, as well as being able to delete an empty ORACLE_HOME is also available in the new UI. Few screens below demonstrate the key changes in the UI associated with this new feature.
Conclusion: The Shared ORACLE_HOME feature fulfills a commonly needed functionality for Gen 2 ExaCC. It also lays a foundation for upcoming functionalities like applying DB/GI updates from the UI and moving databases from one home to another so you can upgrade/downgrade your database from one RU to another.
Screen 1: Gen 2 ExaCC Cloud UI Showing New Resource Database Home
Screen 2: You can now create databases in existing ORACLE HOME
Screen 3: Create Database Screen
Screen 4: Creating new HOME at the same time when new Database is being created
Are you looking for more Gen 2 ExaC@C Blog Posts?
Strategic Product Leader and Technical Architect, owning the global product strategy, development and growth of Oracle’s industry leading product, Exadata Cloud at Customer. Expert at driving the development and launch of future generations of disruptive cloud products for mainstream customers. Extensive experience in conceiving and implementing business processes, managing cross-functional teams across multiple geographies, building strategic partnerships, and program management, supported by a strong Oracle database engineering background.