How to Use Standby Database for Reporting Purposes during Upgrade or Patching Activities on Primary Database
(Doc ID 2438569.1)
Last updated on APRIL 02, 2019
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 11.2 to 12.2]
Information in this document applies to any platform.
The steps needed to apply a patch in a Data Guard configuration are the following note:
How do you apply a Patchset,PSU or CPU in a Data Guard Physical Standby configuration (Doc ID 278641.1)
Since no post installation SQL can be run on a physical standby, the upgrade process is finished at the standby side when the redo generated by the primary during the upgrade are received and applied.
This would require a downtime for both primary and standby databases.
In some cases, the complete unavailability cannot be scheduled. The standby database can be opened read only and used for reporting purposes while the primary is closed due to patching activities.
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