How do you apply a Patchset,PSU or CPU in a Data Guard Physical Standby configuration
(Doc ID 278641.1)
Last updated on MARCH 16, 2022
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 184.108.40.206.0 [Release 10.1 to 19]
Oracle Database Cloud Schema 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
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Would you like to explore this Topic further with other Oracle Customers, Oracle Employees and Industry Experts ??
You can discuss this Note, show your Experiences or ask Questions about it directly right at the Bottom of this Note in the Discussion Thread about this Document.
If you want to discover Discussions about other Articles und Subjects or even post new Discussions you can access the My Oracle Support Community Page for High Availability Data Guard
To apply an Interim Patchset for example the 10.2.0.4 Patchset or January 2010 10.2.0.4 RDBMS PSU, to both the Primary and Standby Sites.
For Dg configuration with Logical Standby Refer, "Upgrading Oracle Database with a Logical Standby Database In Place (Doc ID 437276.1)".
The process of applying the Patchset/PSU/CPU to a Primary and Standby site are same, however post upgrade/patch changes are not applied directly on standby due to the nature of Physical standby(mount/open read only).
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
|To apply an Interim Patchset for example the 10.2.0.4 Patchset or January 2010 10.2.0.4 RDBMS PSU, to both the Primary and Standby Sites.|
|The Interim Patchset application in detail - in this case 10.2.0.4 PSU 3 or Patch 9119284|