My Oracle Support Banner

Oracle Patch Assurance - Data Guard Standby-First Patch Apply (Doc ID 1265700.1)

Last updated on FEBRUARY 10, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Enterprise Manager for Oracle Database - Version 12.1.0.2.0 and later
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
Information in this document applies to any platform.
Reviewed relevance on May 07, 2013 ***

Purpose

 

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

 

Overview

Oracle Data Guard Standby-First Patch Apply provides support for different database home software between a primary database and its physical standby database(s) for the purpose of applying and validating Oracle patches in rolling fashion with minimal risk to the primary database.

Data Guard has long supported running different configuration between primary and standby systems.  Data Guard is completely independent from anything under the database, so you can run different versions of the operating system, Oracle Clusterware, hardware, or storage software across different sites with no restrictions on versions or time.  This has included support for the following:

However, differences in database home software were limited to rolling upgrade scenarios supported only by logical standby databases.  In order to apply a later database home patch (e.g. Exadata bundle patch, or database PSU) to a Data Guard environment with physical standby, you had to perform one of the following actions:

With Data Guard Standby-First Patch Apply, Oracle supports different database home software between a primary database and its physical standby database(s), in addition to the differences listed above.

 

Data Guard Standby-First Patch Apply

Oracle Data Guard Standby-First Patch Apply provides support for different database home software between a primary database and its physical standby database(s) for the purpose of applying and validating Oracle patches and patch bundles in rolling fashion with minimal risk to the primary database. For example, with Data Guard Standby-First Patch Apply you apply a database home patch first to a physical standby database.  The standby is used to run read-only workload, or read-write workload if it is a snapshot standby, for testing and evaluation of the patch.  After passing evaluation, the patch is then installed on the primary system with greater assurance of the effectiveness and stability of the database home patch.

Oracle Data Guard Standby-First Patch Apply is supported only for certified interim patches and patch bundles (e.g. Patch Set Update, or Database Patch for Exadata) for Oracle Database 11.2.0.1 and later, on both Oracle Engineered Systems (e.g. Exadata, SuperCluster) and non-Engineered Systems. A patch and patch bundle that is Data Guard Standby-First certified will state the following in the patch README:

Data Guard Standby-First Installable

The following types of patches are candidates to be Data Guard Standby-First certified:

Patches and patch bundles that update modules that may potentially disrupt the interoperability between primary and physical standby systems running different database home software will not be certified “Data Guard Standby-First Installable” and will not state so in the patch README.

Oracle patch sets and major release upgrades do not qualify for Data Guard Standby-First Patch Apply.  For example, upgrades from 11.2.0.2 to 11.2.0.3 or 11.2 to 12.1 do not qualify.  Use the Data Guard transient logical standby rolling upgrade process for database patch sets and major releases.  Refer to the Oracle Maximum Availability Architecture best practice document at:

http://www.oracle.com/technetwork/database/availability/database-rolling-upgrade-3206539.pdf

Other configuration differences between primary and standby systems listed above in the Overview section that have been previously supported continue to be supported.

Data Guard Standby-First Patch Apply has the following advantages:

 

Note: Oracle Java Virtual Machine (OJVM) updates require special consideration in Standby First Patching.  Please see MOS note 2217053.1 for more information.

 

 

Scope

Applies To

Oracle Exadata Database Machine Release 2 (11.2) release 11.2.0.1 bundle patch 8, and later
Oracle Database 11g Enterprise Edition Release 2 (11.2) release 11.2.0.2, 11.2.0.3 and later 

Details

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
Purpose
 Overview
 Data Guard Standby-First Patch Apply
Scope
 Applies To
Details
 Considerations, Recommendations, and Restrictions
 Steps to Perform Data Guard Standby-First Patch Apply
 Phase 1: Perform Patch Binary Installation on Standby Only
 Phase 2: Evaluate Patch on Standby Database
 Phase 3: Complete Patch Installation or Rollback
 Phase 3 Option 1: Apply Patch to Primary Database
 Phase 3 Option 2: Data Guard Switchover and Apply Patch to New Physical Standby
 Phase 3 Option 3: Rolling Back a Patch on a Standby Database
References

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