Upgrading to 19c Oracle Database with Reduced Downtime Using DBMS_ROLLING on Exadata Database Service (ExaDB)
(Doc ID 2832235.1)
Last updated on OCTOBER 13, 2023
Applies to:
Gen 2 Exadata Cloud at Customer - Version N/A to N/A [Release All Releases]Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A to N/A [Release N/A]
Information in this document applies to any platform.
Goal
This document provides step-by-step instructions for database 19c rolling upgrade with DBMS_ROLLING, from Oracle Database 12.2.0.1 and higher to Oracle Database Release 19c on Exadata Database Service on Dedicated Infrastructure (ExaDB-D) and Exadata Database Service on Cloud@Customer (ExaDB-C@C).
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 |
| Overview |
| Phase 1 - Database 19c DBMS_ROLLING Upgrade Prerequisites |
| Step 1.1 – Validate Upgrade Steps on Test |
| Step 1.2 - Validate Minimum Software Requirements |
| Step 1.2.1 - Golden Gate Supported Versions |
| Step 1.2.2 - Oracle Application Express (APEX) Supported Versions |
| Step 1.2.3 - Required Exadata Database Server Software Version |
| Step 1.2.4 - Required Grid Infrastructure Version |
| Step 1.2.5 - Install the latest Cloud Tooling |
| Step 1.3 - Check the status and version of the primary and standby database |
| Step 1.4 - Check that all data types are supported on a logical standby database |
| Step 1.5 - Run Latest EXAchk and Address Critical Alerts |
| Step 1.6 - Prepare Target 19c Oracle Home on the Primary and Standby Systems |
| Step 1.7 - Run PreUpgrade Information Tool on the Primary Database |
| Step 1.7.1 – Run PreReqs on Primary Database |
| Step 1.7.2 - Review PreUpgrade Information Tool Output |
| Step 1.8 - Evaluate the checklist for continuous application service during the maintenance window |
| Phase 2 – Upgrade the Database to 19c using DBMS_ROLLING |
| Step 2.1 - Planning a Rolling Upgrade |
| Step 2.1.1 – Set the Standby database in MOUNT State |
| Step 2.1.2 – Check the Standby LAG |
| Step 2.1.3 - Initialize the Plan |
| Step 2.1.4 – Display the parameters for the current plan build |
| Step 2.1.5 – Build the Upgrade Plan |
| Step 2.1.6 – Display the Plan |
| Step 2.2 - Performing a Rolling Upgrade |
| Step 2.2.1 - Run Start Plan |
| Step 2.2.2 - Verify that Standby Database is Successfully Converted |
| Step 2.2.3 – Tuning a Logical Standby Database |
| Step 2.2.3.1 – Adjust How Transactions are Applied On the Logical Standby Database |
| Step 2.2.3.2 – Adjust the Number of Processes |
| Step 2.2.4 - Run PreUpgrade Information Tool on the Transient Logical Standby Database |
| Step 2.2.4.1 – Run PreReqs on Transient Logical Standby Database |
| Step 2.2.4.2 - Review PreUpgrade Information Tool Output |
| Step 2.2.5 – Check if Replication is Running on Logical Standby Database |
| Step 2.2.6 - Upgrade the Future Primary Database |
| Step 2.2.7 - Start Logical Standby Apply |
| Step 2.2.8 - Perform the Switchover |
| Step 2.2.9 - Move the New Logical Standby (former primary database) to the New 19c Database Oracle Home |
| Step 2.2.10 - Execute DBMS_ROLLING.FINISH_PLAN |
| Phase 3 - Post Upgrade Steps |
| Step 3.1 – Validate the New Standby Database |
| Step 3.2 - Post DBMS_ROLLING Upgrade Tasks |
| Step 3.3 – Enable Oracle Active Data Guard |
| Step 3.4 – Destroy the DBMS_ROLLING Plan |
| Step 3.5 - Drop Guaranteed Restore Point on Standby and Primary |
| Appendix |
| A – Troubleshooting DBMS_ROLLING Errors |
| B – Troubleshooting Database Upgrade Failure |
| Case 1 - Failure occurs during pre-upgrade |
| Case 2 - Failure occurs during database upgrade |
| Case 3 - Failure occurs during post-upgrade |
| C - Rolling Back a Rolling Upgrade |
| Step C.1 – Stop the Transient Logical Standby |
| Step C.3 – Mount the Transient Logical Standby |
| Step C.4 - Execute DBMS_ROLLING.ROLLBACK_PLAN on the Primary Database |
| Step C.5 – Remove Data Guard Configuration (12.2 only) |
| Step C.6 – Stop the Transient Logical Standby Database |
| Step C.7 - Downgrade the Database in CRS |
| Step C.8 – Restore the original configuration and environment files |
| Step C.9 – Recreate the SPfile |
| Step C.10 - Open the Transient Logical Standby Database |
| Step C.11 – Recreate the Data Guard Configuration (Only for 12.2) |
| Step C.12 – Validate Data Guard Broker Configuration |
| <Internal_Only> |
| D - Known Issues |
| DBUA Postupgrade Service Start Starts Services That Do Not Match Current Database Role |
| </Internal_Only> |
| Revision History |
| References |