How to Update Exadata Database Service in Oracle Cloud to Exadata Image Version 23.x and Oracle Linux 8
(Doc ID 2936828.1)
Last updated on AUGUST 15, 2023
Applies to:
Oracle Database Cloud Exadata Service - Version N/A to N/A [Release 1.0]Oracle Exadata Storage Server Software - Version 23.1.0.0.0 and later
Information in this document applies to any platform.
Goal
The goal of this document is to guide a user of the Exadata Database Service in Oracle Cloud in updating the Exadata System Software on nodes in the VM cluster to Exadata image version 23.x from 22.1/21.2 using a command line patchmgr-based approach.
The preferred approach for updating the Exadata image version is to use the Oracle Cloud Console, but there may be circumstances where the manual approach described in this document is needed, such as the following:
- Updating one node at a time, which may be necessary when customer actions are required on each node before or after the update before proceeding to the next node.
- Updating a subset of nodes at a time.
- Updating all nodes in the VM cluster in a non-rolling manner.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
Introduction |
Overview of Virtual Machine OS Update to Exadata 23.x |
Plan for Virtual Machine OS Update to Exadata Image Version 23.x and Oracle Linux 8 |
Confirm Requirements for Virtual Machine OS Update to Exadata 23.x |
Use the Latest Certified Exadata Image Version |
Confirm Customer-Installed Software Compatibility with Oracle Linux 8 |
Understand the patchmgr Utility |
Achieve Continuous Availability For Your Applications During Virtual Machine OS Updates |
Run Exachk to Validate Overall VM Cluster Health |
Restrictions |
VM Guest File System Encryption |
Scale Compute / Add Node |
Perform Setup and Pre-Upgrade Steps for Virtual Machine OS Update to Exadata Image Version 23.x and Oracle Linux 8 |
Run Precheck from Oracle Cloud Console to Stage Software in the VM Cluster |
Obtain the Names of the Nodes in the VM Cluster |
Select and Configure the Driving System(s) Where patchmgr Will Run |
Select the Driving System(s) |
Configure SSH Equivalence from the Driving System to Nodes in the VM Cluster |
Create the patchmgr Group File on the Driving System |
Run "patchmgr --backup" to Backup Nodes in the VM Cluster |
Stage Updated KMS Library on All Nodes in the VM Cluster |
Run "patchmgr --precheck" to Verify Nodes in the VM Cluster are Prepared for Update |
Handling "patchmgr --precheck" Failure Caused by Customer-Installed Packages |
Update Virtual Machine OS to Exadata Image Version 23.x and Oracle Linux 8 |
Run "patchmgr --upgrade" to Update Nodes in the VM Cluster |
Confirm Updated Exadata Image Version and Status |
Update Customer-Installed Software to OL8-Compatible Versions |
Run "patchmgr --upgrade" on the Next Set of Nodes in the VM Cluster |
(Optional, if required) Rollback Nodes in the VM Cluster to the Prior Version |
Perform Post Update Steps |
Remove Root User SSH Equivalence |
Update Customer-Installed Software to OL8-Compatible Versions |
Known Issues |
References |