Patching and upgrading an On-Premises to Oracle Cloud Standby Database
(Doc ID 2626861.1)
Last updated on DECEMBER 09, 2021
Applies to:
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A to N/A [Release N/A]Information in this document applies to any platform.
Goal
To upgrade or apply a bundle patch to the Cloud standby database in an On-Premises to Oracle Cloud Disaster Recovery configuration. These processes are out-of-place, which is the Oracle recommended method for RDBMS patching and upgrade.
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 |
| Prerequisites |
| Verify the Current Environment |
| Stage the Target RDBMS Software for Patching or Upgrade |
| Create Empty RDBMS Home |
| Apply any one-off or merge patches. |
| Validate the new home version: |
| Run Pre-Checks on Standby DB |
| Patching the Cloud Standby Database |
| Re-Run Pre-Checks on Standby DB |
| Move Customer Created Listeners |
| Move the Standby Database to the Target RDBMS Home |
| For Registered Databases |
| For Un-Registered Databases |
| Patch the Primary Database |
| Verify the Data Guard Broker configuration |
| Upgrading the Standby Database |
| Re-Run Pre-Checks on Standby DB |
| Disable Fast-Start Failover |
| For Source 11.2 Databases ONLY - Disable Data Guard Broker |
| Move Customer Created Listeners |
| Optionally Create a Guaranteed Restore Point |
| Verify the Standby Database is Current with the Primary |
| Move the Standby Database to the Target RDBMS Home |
| For Registered Databases |
| For Un-Registered Databases |
| Upgrade the Primary Database |
| Post Steps after Primary Database Upgrade |
| References |