Patching Exadata Cloud Services
First of all there are different versions of Exadata cloud services
Exadata Cloud @Customer (Gen -1) ( Mostly phased out)
Exadata Cloud on OCI (Gen-2) with MDS support ( this allows for older oracle releases at a support uplift cost)
Exadata Cloud on OCI (Gen-2)
Exadata Cloud at Customer Gen-2
All three have different patch levels that are published.
Oracle has a number of notes to help you understand which patches are appropriate for which type of Exadata Cloud System. You will need an Oracle support ID to view these.
Exadata Database Service Software Versions (Doc ID 2333222.1)
JAN-2024 Patching Guidelines - Oracle Cloud Customers with lower database release version 18c and lower (Doc ID 2997504.1)
Customers who are on MDS have a different process for patching in OCI.
"Starting Jan ’2024, we will not be externalizing quarterly DB/GI cloud images for the lower DB/GI versions (18c, 12.2, 12.1, and 11.2.0.4) to customers on OCI (ExaDB-D, ExaDB-C@C, BaseDB) and OCI-C (OCC, Gen 1 ExaCC, and DBCS) cloud services. Customers on Upgrade Support (previously called MDS) can only provision lower version databases and database homes from Oct 2023(*) and earlier.
To create a Jan 2024 or later lower version database or database home, Upgrade Support customers must first deploy Oct 2023(*) or earlier database home and using opatch, apply the January 2024 or later RU to update the database or home.
Recommended by LinkedIn
Upgrade Support customers can continue to get Jan 2024 and newer RU/one-off patches on lower DB/GI versions (18c, 12.2, 12.1, and 11.2) for DB Cloud services on OCI and OCI-C cloud services from MOS. However, they will not be able to use cloud automation to patch database homes. Rather they will need to use opatch to apply the updates they download from MOS."
Gen 1 Exadata Cloud at Customer Update instructions available in Document 2391164.1.
Please note that Oracle themselves will take care of patching the Storage layer, Infiniband and the Dom0 or hypervisor of the systems. As they do this in a rolling fashion you will be made aware of the patching taking place but there will not be a interruption of service to the database as a whole since one db node will go offline at a time. However if you have dedicated services to individual nodes of your RAC cluster then you will not have the requisite High availability setup and you may suffer some disruption. for this reason it is essential to use services that can be migrated between nodes as required rather than sids.
For DomU it is important to have full backups of all databases in place. please ensure that your grid software versions and DB versions are compatible with the image you are trying to apply. Please not that the images for the Exadata cloud service are provided in the notes given above you should not try to use any version that is not yet compatibility tested . For example version 19c and later is only available for Gen 2 cloud at present . It is not available for the Gen 1 cloud.
Please check here for a comprehensive overview of Exadata Cloud
Exadata Cloud Support Information Center (Doc ID 2522950.2)
© 2025 Robin Saikat Chatterjee . All rights reserved. The opinions in these pages are my own and do not reflect those of my Employer Tata Consultancy Services. Follow me on Linkedin