My Oracle Support Banner

Upgrading and Opening a Physical Standby when the Primary has failed during upgrade (Doc ID 975614.1)

Last updated on APRIL 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 10.2 to 11.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database 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.


The following has occurred in this environment:

1. An attempt has been made to upgrade the Primary from to This has failed.

2. A Physical Standby Database is in place and attempts are being made to activate the Standby Site.

3. The Standby Site has had the Patchset applied however the RDBMS itself is still

4. The requirement here is to recover the Standby Site to a point where it is synchronised and the open it with the upgrade switch where catupgrd.sql can be run to upgrade the RDBMS and then open it read write.


An upgrade of the Primary Site Binaries  to has been performed.  The RDBMS itself is still

An upgrade of the Standby Site Binaries to has been performed.  The RDBMS is still at

Managed Recovery was disabled prior  to attempting to perform the upgrade and no new redo has been generated from the primary other that occurring prion to upgrade.  Standby Redo logs are in place however real time apply is not in use.


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

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