All members of a Data Guard configuration must run an Oracle image that is built for the same platform.
For example, this means a Data Guard configuration with a primary database on a 32-bit Linux on Intel system
can have a standby database that is configured on a 32-bit Linux on Intel system. However, a primary database
on a 64-bit HP-UX system can also be configured with a standby database on a 32-bit HP-UX system,
as long as both servers are running 32-bit images.

In addition to general support when using the same Oracle platform, Data Guard Redo Apply (physical standby) can support specific mixed Oracle Platform combinations. Oracle Platform IDs, platform names, and which combinations of platform ID(s) that can be combined to form a supported Data Guard configuration using Redo Apply are listed in the table below. Platform combinations not listed in the table below are not supported using Data Guard Redo Apply.

Table Notes

Prior to Data Guard 11g, the Data Guard Broker did not support different word-size in the same Data Guard configuration, thus requiring management from the SQL*Plus command line for mixed word-size Data Guard configurations. This restriction is lifted from Data Guard 11g onward.

Both primary and standby databases must be set at the same compatibility mode as the minimum release (if specified) in the table below.

A standby database cannot be open read-only in any environment that has binary-level PL/SQL-related incompatibilities between primary and standby databases. Support Note 414043.1 is referenced in the table below for any platform combinations where this is the case (the note provides instructions for eliminating incompatibilities post role transition). It is possible to access a standby database in such environments in Oracle Database 11g by temporarily converting it to a Snapshot Standby database, or in Oracle Database 10g by opening the standby read/write as described in the Data Guard 10g Concepts and Administration guide: Using a Physical Standby Database for Read/Write Testing and Reporting. Both procedures require following the steps in note 414043.1 before making the database available to users.

Please be sure to read Support Notes when referenced in the table below.

RMAN generally supports instantiation of a physical standby database for the supported platform combinations. Please see Support Note 1079563.1 for details.

Platforms in a supported combination may operate in either the primary or standby role.

Enterprise Manager can not be used for standby database creation or other administrative functions in any configuration where PLATFORM_IDs are not identical. Oracle recommends using the Data Guard Broker command line interface (DGMGRL) to administer mixed platform combinations from Oracle Database 11g onward and SQL*Plus command line for configurations that pre-date Oracle Database 11g.

PLATFORM_ID

PLATFORM_NAME
Release name

PLATFORM_IDs supported within the same Data Guard configuration when using Data Guard Redo Apply (Physical Standby)

Logical Standby

In addition to general support when using the same Oracle platform, Data Guard SQL Apply (logical standby) can support specific mixed Oracle Platform combinations as of Oracle Database 11g. Oracle Platform IDs, platform names, and which combinations of platform ID(s) that can be combined to form a supported Data Guard configuration using SQL Apply are listed in the table below. Platform combinations not listed in the table below are not supported using Data Guard SQL Apply.

Table Notes

All mixed platform combinations for SQL Apply in the table below are supported from Oracle Database 11g onward.

Prior to Data Guard Broker 11g, the Data Guard Broker did not support different word-size in the same Data Guard configuration, thus requiring all management from the SQL*Plus command line. This restriction is lifted from Data Guard 11g onward.

Both primary and standby databases must be set at the same compatibility mode as the minimum release (if specified) in the table below.

Please be sure to read Support Notes when referenced in the table below.

RMAN generally supports instantiation of a physical standby database for the supported platform combinations. Please see Support Note 1079563.1 for details.

Platforms in a supported combination may operate in either the primary or standby role unless otherwise specified.

Enterprise Manager can not be used for standby database creation or other administrative functions in any configuration where PLATFORM_IDs are not identical. Oracle recommends using the Data Guard Broker command line interface (DGMGRL) to administer mixed platform combinations from Oracle Database 11g onward and SQL*Plus command line for configurations that pre-date Oracle Database 11g.

PLATFORM_ID

PLATFORM_NAME
Release name

PLATFORM_IDs supported within the same Data Guard configuration when using Data Guard SQL Apply (Logical Standby)

2

Solaris[tm] OE (64-bit)
Solaris Operating System (SPARC) (64-bit)

2

3

HP-UX (64-bit)
HP-UX PA-RISC

3, 4

4

HP-UX IA (64-bit)
HP-UX Itanium

3, 4

5

HP Tru64 UNIX
HP Tru64 UNIX

5

6

AIX-Based Systems (64-bit)
AIX5L

6

7

Microsoft Windows (32-bit)
Microsoft Windows (x86)

7, 10
8, 12 – Replication can only occur from a 32-bit primary to a 64-bit standby, once a role transition has promoted the 64-bit system to the primary role, the original 32-bit primary is not supported as a standby database.

8

Microsoft Windows IA (64-bit)
Microsoft Windows (64-bit Itanium)

7 – Replication can only occur from a 32-bit primary to a 64-bit standby, once a role transition has promoted the 64-bit system to the primary role, the original 32-bit primary is not supported as a standby database.
8, 11, 12, 13

9

IBM zSeries Based Linux
z/Linux

9

10

Linux (32-bit)
Linux x86

7, 10
11, 13 – Replication can only occur from a 32-bit primary to a 64-bit standby, once a role transition has promoted the 64-bit system to the primary role, the original 32-bit primary is not supported as a standby database.

11

Linux IA (64-bit)
Linux Itanium

10 – Replication can only occur from a 32-bit primary to a 64-bit standby, once a role transition has promoted the 64-bit system to the primary role, the original 32-bit primary is not supported as a standby database.
8, 11, 13

12

Microsoft Windows 64-bit for AMD
Microsoft Windows (x86-64)

7 – from Oracle 11g onward. Replication can only occur from a 32-bit primary to a 64-bit standby, once a role transition has promoted the 64-bit system to the primary role, the original 32-bit primary is not supported as a standby database.
8, 12

13

Linux 64-bit for AMD
Linux x86-64

10 – Replication can only occur from a 32-bit primary to a 64-bit standby, once a role transition has promoted the 64-bit system to the primary role, the original 32-bit primary is not supported as a standby database.
8, 11, 13