My Oracle Support Banner

Exadata Cloud Database 19c Rolling Upgrade With DBMS_ROLLING (Doc ID 2832235.1)

Last updated on SEPTEMBER 23, 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.


This document provides step-by-step instructions for database 19c rolling upgrade with DBMS_ROLLING, from Oracle Database and higher to Oracle Database Release 19c on Exadata Cloud Service (ExaCS) and Exadata Cloud at Customer Gen2 (ExaCC)


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
 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 - Run Start Plan
 Step 2.2.2 - Verify that Standby Database is Successfully Converted
 Step 2.2.3 – Run PreUpgrade Information Tool on the Transient Logical Standby Database
 Step – Run PreReqs on Transient Logical Standby Database
 Step - Review PreUpgrade Information Tool Output
 Step 2.2.4 – Check if Replication is Running on Logical Standby Database
 Step 2.2.5 - Upgrade the Future Primary Database
 Step 2.2.6 - Start Logical Standby Apply
 Step 2.2.7 - Perform the Switchover
 Step 2.2.8 - Move the New Physical Standby (former primary database) to New 19c Database Oracle Home
 Step 2.2.9 - 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 – 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
 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
 Revision History

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.