Rolling upgrade using DBMS_ROLLING - Complete Reference
(Doc ID 2086512.1)
Last updated on DECEMBER 17, 2023
Applies to:
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and laterOracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Goal
Table of Contents
1. Introduction
1.1 Transient Rolling Upgrade Overview
1.2 DBMS_ROLLING
2. Prerequisites
3. Upgrade Steps
3.1. Start
3.2. Upgrade Leading Group
3.3. Switchover
3.4. Upgrade Trailing Group
3.5. Finish
4. Monitoring
5. Example
6. Conclusion
This Document offers step by step method to perform rolling Upgrade using 12c New Feature DBMS_ROLLING pl/sql. For disaster recovery and high availability Oracle recommends having physical standby. However upgrading Data guard environment having physical standby the down time is considerably high. Why because of the nature of physical standby (mount or read only mode). During upgrade time, transaction cannot happen in an upgrading PRODUCTION or Physical standby. The best solution to minimize downtime is Transient Rolling Upgrade using Logical Standby. Since the logical standby is in open READ WRITE mode it is independent of production upgrade unlike Physical Standby.
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 |
References |