My Oracle Support Banner

Mixed Oracle Version support with Data Guard Redo Transport Services (Doc ID 785347.1)

Last updated on FEBRUARY 01, 2022

Applies to:

Oracle Database - Enterprise Edition - Version and later
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 Backup Service - Version N/A and later
Information in this document applies to any platform.
Oracle Server Enterprise Edition - Version: and later


The following is the Support Statement for mixed Oracle RDBMS Version Support with Data Guard Redo Transport Services. 

Mixed Version Support means Combinations of any Version, Major Release or Patchset.  For Example:

  • to or higher
  • to or higher
  • to or higher
  • to or higher
  • to or higher
  • to or higher
  • to or higher
  • etc
  • through current 19c version

  • GoldenGate and Streams DownStream Capture
    • Mixed Version Support to a GoldenGate or Streams Downstream Capture Target Database is supported over an extended Time Period.
      • The COMPATIBLE Parameter of the Target Database must be equal to or greater than the Source Database COMPATIBLE Setting.
  • Logical Standby
    • Mixed Version Support to a Data Guard Logical Standby for Rolling Upgrade is supported (starting from over an extended Time Period.
      • The COMPATIBLE Initialization Parameter of the Primary database must be at the version of the Oracle software being upgraded and the Logical Standby database's COMPATIBLE setting must either match that of the Primary Database or be higher.
  • Physical Standby
    • Mixed Version Support between a Primary database and a Data Guard Physical Standby is NOT supported at all until Oracle Database  From Oracle Database it is possible to configure the Physical Standby database with at a higher patchset or major release Primary database for purposes of a migration to new hardware provided that after a switchover to that standby, the database is not allowed to open and is immediately upgraded in the normal manner. 
    • In addition, starting with Oracle Database a Physical Standby database can run at a higher PSE, CPU or PSU for the purposes of Standby First Patching.  See the note below for more information.

      Note: Starting with it is possible to have a Physical Standby at a higher Patchlevel (Patch, CPU, PSU, BP) when the README of the Patch states that it is valid for Standby First Patching. Please see "Oracle Patch Assurance - Data Guard Standby-First Patch Apply (Doc ID 1265700.1)" for more information.

Note that in the supported Cases, the Primary/Source Database is at a lower version, and the Standby/Target Database is at a higher Version.


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.