Oracle Exadata Database Service 19c Rolling Upgrade with DBMS_ROLLING from Oracle Database 12.1.0.2
(Doc ID 2889464.1)
Last updated on AUGUST 15, 2022
Applies to:
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A to N/A [Release N/A]Gen 2 Exadata Cloud at Customer - Version N/A to N/A [Release All Releases]
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.1.0.2 to Oracle Database Release 19c on Oracle Exadata Database Service on Dedicated Infrastructure and Exadata Cloud at Oracle Exadata Database Service on Cloud@Customer.
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.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 checklist for continuous application service during 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 - Disable Data Guard Broker |
| Step 2.2.2 - Run Start Plan |
| Step 2.2.3 - Open and Verify that the Standby Database is Successfully Converted |
| Step 2.2.4 - Start Apply in the Transient Logical Standby Database |
| Step 2.2.5 - Run PreUpgrade Information Tool on the Transient Logical Standby Database |
| Step 2.2.5.1 – Run PreReqs on Transient Logical Standby Database |
| Step 2.2.5.2 - Review PreUpgrade Information Tool Output |
| Step 2.2.6 - Upgrade the Standby Database |
| Step 2.2.7 - Start Logical Standby Apply |
| Step 2.2.8 - Perform the Switchover |
| Step 2.2.9 - Modify the Database Roles |
| Step 2.2.10 - Move the New Physical Standby (former primary database) to New 19c Database Oracle Home |
| Step 2.2.11 - Enable Data Guard Broker Start and Mount the New Standby as Single Instance |
| Step 2.2.12 - Execute DBMS_ROLLING.FINISH_PLAN and Enable Data Guard Broker |
| Step 2.2.13 – Start all the Database Instances |
| 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 (Optional) |
| Step 3.4 – Switchover the database roles |
| Step 3.5 - Validate the version and statuses of the databases |
| Step 3.6 – Destroy the DBMS_ROLLING Plan |
| Step 3.7 - Drop Guaranteed Restore Point on Standby and Primary |
| Revision History |
| References |