Using logical standby to rolling upgrade database from 11.1 to 11.2
(Doc ID 1557249.1)
Last updated on JUNE 16, 2021
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
The purpose of this document is to show steps on how to perform a rolling upgrade, and the expected messages in the alert logs
The goal is rolling upgrade from 184.108.40.206 to 220.127.116.11.
The broker on these database are configured, but the dg_broker_start parameter is set to "FALSE", so the recovery should not start even the DB restart.
from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material.
Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
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