Exadata Cloud: Updating ExaCC DB Node GI and DB Software Precheck/Patch workflow
(Doc ID 2603939.1)
Last updated on FEBRUARY 08, 2022
Applies to:
Oracle Database Cloud Exadata Service - Version N/A to N/A [Release 1.0]Oracle Cloud Infrastructure - Version N/A to N/A [Release 1.0]
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A to N/A [Release N/A]
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A to N/A
Information in this document applies to any platform.
Purpose
In this document we will review workflows for updating the ExaCC DB Node GI and DB Software via Cloud UI and via Command Line
Scope
1. Checklists
2. GI Patching from UI – Workflow
- GI Patching from UI – Precheck Workflow
- GI Patching from UI – Patch Workflow
- Some key considerations
3. DB Service Patching using the Cloud UI
- DB Service Patching from UI – Precheck Workflow
- DB Service Patching from UI – Patch Workflow
- Shared Home DB Service Patching from UI – Patch Workflow
- Patching shared Oracle Home using the Cloud UI
- Some key considerations
- Rolling back GI/DB PSU Patch using the Cloud UI
4. ExaCC GI/DB Patching using the command line
- Why use command line patching?
- Scenario: Patch one node at a time
- Scenario: Shared Oracle Home and not able to create new Home (If OCC < 18.1.4.4)
- Scenario: Patch all DBs which are part of Shared Oracle Home together
- Scenario: DB Instance subsetting (RAC DB instance not configured on all Nodes of Cluster)
- Update UI after command line patching
5. What to do if precheck or patch job fails
6. Database Server Software Maintenance Best Practices
Details
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
| Purpose |
| Scope |
| Details |
| References |