Oracle DG（Data Guard）支持异构平台说明

时间 2021-04-10

标签 node 数据库服务器 app less ide post 测试 this 栏目 Oracle 繁體版

原文原文链接

Oracle DG（Data Guard）支持异构平台说明

一.说明

OracleData Guard 最简单的配置是主备库的环境都同样，可是在有些状况下须要异构的配置，好比在迁移时为了减小停机时间或者零停机，可能就须要使用异构的DG 配置。node

关于Oralce DataGuard 异构平台的搭建，MOS上有2篇文章专门来讲明：数据库

Data Guard Support for HeterogeneousPrimary and Logical Standbys in Same Data Guard Configuration [ID 1085687.1]服务器

Data Guard Support for HeterogeneousPrimary and Physical Standbys in Same Data Guard Configuration [ID 413484.1]app

Prior to DataGuard 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. Thisrestriction is lifted from Data Guard 11g onward.less

--在Oracle 11g 以前，DG Broker 不支持不一样word-size的DG 配置，所以须要修改word-size. 到了Oracle 11g 以后，DG 就没有了这个限制。ide

Changing between 32-bit and 64-bit WordSizes [ID 62290.1]post

这里的word-size 只的是数据库的位数，是32位仍是64位。其查看方法，我以前的Blog 有说明。测试

查看Oracle 是32位仍是64位的方法ui

http://blog.csdn.net/tianlesoftware/article/details/6818709this

在配置异构DG 以前，要先查看主备库的Platform. ID,能够从v$database 视图中查看：

SQL> select platform_id,platform_name from v$database;

PLATFORM_ID PLATFORM_NAME

----------- ---------------------------------------------

7 Microsoft Windows IA (32-bit)

SQL> select platform_id,platform_name from v$database;

PLATFORM_ID PLATFORM_NAME

-------------------------------------------------------------------------------

10 Linux IA (32-bit)

这里的Platform_ID 是惟一的，不一样的平台，即OS 对应一个ID。

Differencesbetween the primary server(s) and the standby server(s) are always supported aslong as the Oracle software installed on all servers is of the same OraclePlatform. as defined above, is certified to run on each server, and is the sameOracle Database Release and Patch Set. Examples of such differences that aresupported include the following:

--只要server 上Oracle 的软件的版本和位数是一致的，主备库就支持不一样的server，即OS 不影响，好比：

（1）Hardware manufacturer (e.g. Delland Sun or Hitachi and EMC)

（2）Hardware configuration (e.g. numberof CPUs, amount of RAM, storage configuration, etc)

（3）Processor (e.g. x86-64 AMD64 andx86-64 Intel 64; POWER4 and POWER5)

（4）Operating system distribution (e.g.Red Hat Linux, SUSE Linux or Oracle Enterprise Linux)

（5）Operating system version (e.g.Windows 2000 and Windows XP)

二.物理standby

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

--物理standby 支持的混合平台以下表所列，不在下表不受支持。

Table Notes –表格注释

(1) Prior to Data Guard 11g, theData Guard Broker did not support different word-size in the same Data Guardconfiguration, thus requiring management from the SQL*Plus command line formixed word-size Data Guard configurations. This restriction is lifted fromData Guard 11g onward.

--在Oracle 11g以后，不受数据库word-size的限制（数据库32仍是64位）

(2) Both primary and standbydatabases must be set at the same compatibility mode as the minimum release (ifspecified) in the table below.

--在下表所列的平台中，主备库的compatible 参数必须相同。

(3) A standby database cannot beopen read-only in any environment that has binary-level PL/SQL-relatedincompatibilities between primary and standby databases. Support Note414043.1 is referenced in the table below for any platform. combinations wherethis is the case (the note provides instructions for eliminatingincompatibilities post role transition). It is possible to access astandby database in such environments in Oracle Database 11g by temporarilyconverting it to a SnapshotStandby database, or in Oracle Database 10g by opening the standbyread/write as described in the Data Guard 10g Concepts and Administrationguide: Usinga Physical Standby Database for Read/Write Testing and Reporting. Bothprocedures require following the steps in note 414043.1 before making thedatabase available to users.

(4) Please be sure to read SupportNotes when referenced in the table below.

(5) RMAN generally supportsinstantiation of a physical standby database for the supported platformcombinations. Please see Support Note 1079563.1 for details.

(6) Platforms in a supportedcombination may operate in either the primary or standby role.

--平台支持主备库角色的转换

(7) Enterprise Manager can not beused for standby database creation or other administrative functions in anyconfiguration where PLATFORM_IDs are not identical. Oracle recommends using theData Guard Broker command line interface (DGMGRL) to administer mixed platformcombinations from Oracle Database 11g onward and SQL*Plus command line forconfigurations that pre-date Oracle Database 11g.

--在PLATFORM_ID 不同的状况下，备库不能建立和使用EM。但可使用DG Broker。

PLATFORM_ID	PLATFORM_NAME Release name	PLATFORM_IDs supported within the same Data Guard configuration when using Data Guard Redo Apply (Physical Standby)
2	Solaris[tm] OE (64-bit) Solaris Operating System (SPARC) (64-bit)	2 6 - This is not supported due to issues reported in Bug 12702521
3	HP-UX (64-bit) HP-UX PA-RISC	3 4 - Oracle 10g onward, see Support Notes 395982.1 and 414043.1
4	HP-UX IA (64-bit) HP-UX Itanium	4 3 - Oracle 10g onward, see Support Notes 395982.1 and 414043.1
5	HP Tru64 UNIX HP Tru64 UNIX	5
6	IBM AIX on POWER Systems (64-bit)	2 - This is not supported due to issues reported in Bug 12702521 6
7	Microsoft Windows (32-bit) Microsoft Windows (x86)	7 8, 12 - Oracle 10g onward, see Support Note 414043.1 10 - Oracle 11g onward, requires patch for Bug 13104881 11, 13 - Oracle 11g onward, see Support Note 414043.1, also requires patch for Bug 13104881
8	Microsoft Windows IA (64-bit) Microsoft Windows (64-bit Itanium)	7 - Oracle 10g onward, see Support Note 414043.1 8 12 - Oracle 10g onward 11, 13 - Oracle 11g onward, requires patch for Bug 13104881
9	IBM zSeries Based Linux z/Linux	9 18 (64-bit zSeries only)
10	Linux (32-bit) Linux x86	7 - Oracle 11g onward, requires patch for Bug 13104881 10 11, 13 - Oracle 10g onward, see Support Note 414043.1
11	Linux IA (64-bit) Linux Itanium	10 - Oracle 10g onward, see Support Note 414043.1 11 13 - Oracle 10g onward 7 - Oracle 11g onward, see Support Note 414043.1, also requires patch for Bug 13104881 8, 12 - Oracle 11g onward, requires patch for Bug 13104881
12	Microsoft Windows 64-bit for AMD Microsoft Windows (x86-64)	7 - Oracle 10g onward, see Support Note 414043.1 8 - Oracle 10g onward 12 11, 13 - Oracle 11g onward, requires patch for Bug 13104881
13	Linux 64-bit for AMD Linux x86-64	7 - Oracle 11g onward, see Support Note 414043.1, also requires patch for Bug 13104881 10 - Oracle 10g onward, see Support Note 414043.1 11 - Oracle 10g onward 8, 12 - Oracle 11g onward, requires patch for Bug 13104881 13 20 - Oracle 11g onward
15	HP Open VMS HP OpenVMS Alpha HP IA OpenVMS OpenVMS Itanium	15
16	Apple Mac OS Mac OS X Server	16
17	Solaris Operating System (x86) Solaris Operating System (x86)	17 20 - Oracle 10g onward, see Support Note 414043.1
18	IBM Power Based Linux Linux on Power	9 (64-bit zSeries only) 18
20	Solaris Operating System (AMD64) Solaris Operating System (x86-64)	13 - Oracle 11g onward 17 - Oracle 10g onward, see Support Note 414043.1 20

对表格查看的解释，这里举一例，假设准备搭建一个物理DG：

主库：7（platform. id） Microsoft Windows IA (32-bit)

备库：10 （platform. id） Linux IA (32-bit)

7

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

7
 8, 12 - Oracle 10g onward, see Support Note 414043.1
 10 - Oracle 11g onward, requires patch for Bug 13104881
 11, 13 - Oracle 11g onward, see Support Note 414043.1, also requires patch for Bug 13104881

从这里能够看出，7支持的备库有7，8，12，10，11，13. 可是不一样的版本也有限制。咱们的备库要用10，那么只能是Oracle 11g 之后才支持，而且还须要修复13104881的bug。

Additional information:

Transient Logical Database Rolling Upgrades: Beginning withOracle Database 11.1.0.7, a physical standby database can be used to execute arolling database upgrade to a new Oracle Patch Set or database release by usingthe transient logical rolling database upgrade process. See the MaximumAvailability Architecture Best Practice paper, " Rolling Database Upgrades for PhysicalStandby Databases using Transient Logical Standby 11g". Thedatabase rolling upgrade process enables a standby database to apply redo sentby a primary database that is operating at a previous Oracle release orpatchset. The transient logical rolling upgrade process requires that theprimary and standby platform. combination be a supported configuration for bothRedo Apply (see table above) and SQL Apply (see Support Note 1085687.1) as ofthe pre-upgrade Oracle release deployed in the Data Guard configuration.

DataGuard Configurations that Include a Combination of Physical and Logical StandbyDatabases: A Data Guardconfiguration includes a primary database and up to 30 standby databases.These standby databases may be a mix of physical and logical standby databases.All physical standby databases within a single Data Guard configuration mustadhere to the requirements described in this note. Likewise, if theconfiguration includes logical standby databases, they must conform. to therequirements of Support Note 1085687.1.

Real Application Cluster &Automatic Storage Management: It isnot necessary that the primary and the standby both be Oracle RAC databases, orboth use ASM. For example, the primary database may be running Oracle RAC withor without ASM, and the standby database(s) may be single-instance, with orwithout ASM. Also, in case both the primary and standby are Oracle RACdatabases, the number of Oracle RAC nodes between the primary and standbydatabases may vary. Furthermore, the versions of ASM and CRS do not need to bethe same between the primary and standby systems.

ExadataDatabase Machine: It istransparent to Data Guard whether primary and/or standby databases reside on anExadata Database Machine or on other hardware, as long as the platform. ID's ofprimary and standby systems within the same Data Guard configuration conform. tothe support requirements defined in the above table. If Exadata HybridColumnar Compression (EHCC) is used, it is strongly recommended that bothprimary and standby databases reside on Exadata. See the Maximum AvailabilityArchitecture Best Practice paper, "Disaster Recovery for Exadata Database Machine".

三.逻辑standby

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

--逻辑standby 支持以下的平台

Table Notes – 表格注释

(1) All mixed platform. combinationsfor SQL Apply in the table below are supported from Oracle Database 11g onward.

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

(3) Both primary and standbydatabases must be set at the same compatibility mode as the minimum release (ifspecified) in the table below.

(4) Please be sure to read SupportNotes when referenced in the table below.

(5) RMAN generally supportsinstantiation of a physical standby database for the supported platformcombinations. Please see Support Note 1079563.1 for details.

(6) Platforms in a supportedcombination may operate in either the primary or standby role unless otherwisespecified.

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 requires patch for Bug 13104881 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, 12 11, 13, both require patch for Bug 13104881
9	IBM zSeries Based Linux z/Linux	9
10	Linux (32-bit) Linux x86	7, requires patch for Bug 13104881 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, requires patch for Bug 13104881 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, requires patch for Bug 13104881 11, 13
15	HP Open VMS HP OpenVMS Alpha HP IA OpenVMS OpenVMS Itanium	15
16	Apple Mac OS Mac OS X Server	16
17	Solaris Operating System (x86) Solaris Operating System (x86)	17
18	IBM Power Based Linux Linux on Power	18
20	Solaris Operating System (AMD64) Solaris Operating System (x86-64)	20

Additional information:

Mixing Database Versions During Database Rolling Upgrades:Beginning with Oracle Database 10.1.0.3 and onward, a logical standby databasecan operate at a later Oracle release than on the primary when using SQL Applyto execute a rolling database upgrade. Please refer to "Rolling Database Upgrades using Data GuardSQL Apply", " Rolling Database Upgrades for PhysicalStandby Databases using Transient Logical Standby 11g",

DataGuard Configurations that Include a Combination of Physical and Logical StandbyDatabases: A Data Guardconfiguration includes a primary database and up to 30 standby databases.These standby databases may be a mix of physical and logical standby databases.All logical standby databases within a single Data Guard configuration mustadhere to the requirements described in this note. Likewise, if theconfiguration includes physical standby databases, they must conform. to therequirements of Support Note 413484.1.

Real Application Cluster &Automatic Storage Management: It isnot necessary that the primary and the standby both be Oracle RAC databases, orboth use ASM. For example, the primary database may be running Oracle RAC withor without ASM, and the standby database(s) may be single-instance, with orwithout ASM. Also, in case both the primary and standby are Oracle RACdatabases, the number of Oracle RAC nodes between the primary and standbydatabases may vary. Furthermore, the versions of ASM and CRS do not need to bethe same between the primary and standby systems.

Exadata Database Machine: It is transparent to Data Guardwhether primary and/or standby databases reside on Exadata Database Machine oron other hardware, as long as the platform. ID's of primary and standby systemswithin the same Data Guard configuration conform. to the support requirementsdefined in the above table. If Exadata Hybrid Columnar Compression isused, it is strongly recommended that both primary and standby databases resideon Exadata storage. Note that Data Guard SQL Apply adds support for EHCC inOracle Database 11.2.0.2. See the Maximum Availability Architecture BestPractice paper, "Disaster Recovery for Exadata Database Machine".

在物理 Data Guard 中对异构主备系统的支持 (文档 ID 1602437.1)

Data Guard中主数据库与物理备用数据库（Redo Apply）之间能够有什么差异？

本说明针对重作应用和 Oracle Data Guard 12 发行版 1 进行了更新。它适用于 Oracle Database 10g 和 Oracle Database 12c 的全部版本。

您是否但愿与其余 Oracle 客户、Oracle 员工和业内专家进一步探讨此主题？

您能够直接在本说明底部关于本文的讨论帖子中讨论本说明，介绍您的经验，也能够直接提出相关问题。

若是您但愿就其余文章和话题进行讨论，或者展开新的讨论，您能够访问中文数据库社区。

有关使用逻辑备用数据库（SQL Apply）的支持配置信息，请参阅技术支持Note 1085687.1

范围和适用性：

部署 Data Guard 时最简单的途径是配置同构的对称主/备用配置。可是，为了利用运行不一样操做系统的现有服务器，或者为了在尽量减小停机时间或风险的状况下帮助从一个平台向另外一个平台移植时，一般部署异构配置会很是有用。对于但愿使用低于生产环境的处理能力的配置或者使用成本低于其主系统的组件来配置备用系统，从而减小其灾难恢复投资的用户而言，这是至关合理的选择。使用本技术支持文档中提供的指示和信息来肯定单个 Data Guard 配置中支持哪些平台组合以及可能存在的任何其余要求或限制。

若是考虑使用异构主/备配置，则 Oracle 建议用户进行足够的测试以确保在 switchover（切换）或 failover（故障转移）到备用系统以后，可以继续达到所需的服务水平。

1. 肯定主数据库和备用数据库的平台 ID。

使用如下查询可在 V$DATABASE 视图中找到数据库的PLATFORM_ID：

SQL> select platform_id, platform_name from v$database;

PLATFORM_ID PLATFORM_NAME
----------- -----------------------------------
10 Linux IA (32-bit)

只要知足如下条件，则始终支持主服务器与备用服务器之间的差异：在全部服务器上安装的 Oracle 软件是相同Oracle平台（如上定义）；通过认证可在各服务器上运行；具备相同的 Oracle 数据库发行版和 Patch Set（补丁程序集）。支持的这种差异的示例包括：

硬件生产商（例如 Dell 和 Sun 或 Hitachi 和 EMC）
硬件配置（例如，CPU 数、RAM 大小、存储配置等）
处理器（例如 x86-64 AMD64 和 x86-64 Intel 64；POWER4 和 POWER5）
操做系统发行版（例如 Red Hat Linux、SUSE Linux 或 Oracle Enterprise Linux）
O操做系统版本（例如 Windows 2000 和 Windows XP）

2. 若是您的主平台与备用平台的平台 ID 不一样，请检查下表以查看 Data Guard 重作日志应用（物理备用）是否支持您的配置。

除了在使用相同 Oracle 平台时的通常支持以外，Data Guard 重作日志应用（物理备用）能够支持特定的混合 Oracle 平台组合。下表中列出了 Oracle 平台 ID、平台名称以及哪些平台 ID 能够组合以构成支持的 Data Guard 配置来使用重作日志应用。下表中未列出的平台组合不支持使用 Data Guard 重作日志应用。

表注释

在 Data Guard 11g 以前，Data Guard Broker在相同 Data Guard 配置中不支持不一样的字长，于是须要从 SQL*Plus 命令行管理混合字长的 Data Guard 配置。从 Data Guard 11g 开始消除了此限制。
主数据库和备用数据库必须设置为与下表中最低发行版（若是指定）相同的兼容性模式。
在任何环境中，若是主数据库和备用数据库之间存在与二进制级别相关的 PL/SQL 不兼容，则备用数据库没法以只读模式打开。下表中引用了文档 Note:414043.1，介绍这种状况的任意平台组合（该说明提供有关在角色转换后消除不兼容性的指导）。在 Oracle Database 11g 的这种环境中，能够经过将其临时转换为 Snapshot（快照）备用备用数据库来的方式来访问备用数据库，而在 Oracle Database 10g 中，则按照《Data Guard 10g Concepts and Administration guide》中的如下章节所述来以读/写方式打开备用数据库：Using a Physical Standby Database for Read/Write Testing and Reporting。这两种方法须要遵照 Note:414043.1 中的步骤操做才能使数据库对用户可用。
请确保阅读了下表中引用的技术支持文档。.
对于所支持平台组合，RMAN 一般支持物理备用数据库的实例化。有关详细信息，请参阅技术支持 Note 1079563.1。
支持组合中的平台可以以主或备用的角色运行。
在具备不一样 PLATFORM_ID 的任意配置中，Enterprise Manager 不能用于备用数据库建立或其余管理功能。Oracle 建议使用 Data Guard Broker命令行界面 (DGMGRL) 来管理 Oracle Database 11g 及更高版本的混合平台组合，Oracle Database 11g 以前的配置则使用 SQL*Plus 命令行界面。

PLATFORM_ID	PLATFORM_NAME 发行版名称	使用 Data Guard 重作日志应用（物理备用）时，相同 Data Guard 配置中支持的 PLATFORM_ID
2	Solaris[tm] OE (64-bit) Solaris Operating System (SPARC) (64-bit)	2 6 - 请参考文档 Note: 1982638.1 和 Note: 414043.1
3	HP-UX (64-bit) HP-UX PA-RISC	3 4 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 395982.1 和 Note:414043.1
4	HP-UX IA (64-bit) HP-UX Itanium	4 3 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 395982.1 和 Note:414043.1
5	HP Tru64 UNIX HP Tru64 UNIX	5
6	IBM AIX on POWER Systems (64-bit)	2 - 请参考文档 Note: 1982638.1 和 Note: 414043.1 6
7	Microsoft Windows (32-bit) Microsoft Windows (x86)	7 8, 12 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 414043.1 10 - Oracle 11g 及更高版本，须要 Patch 13104881 11, 13 - Oracle 11g 及更高版本，请参阅技术支持文档 Note: 414043.1，还须要 Patch 13104881
8	Microsoft Windows IA (64-bit) Microsoft Windows (64-bit Itanium)	7 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 414043.1 8 12 - Oracle 10g 及更高版本 11, 13 - Oracle 11g 及更高版本，须要 Patch 13104881
9	IBM zSeries Based Linux z/Linux	9 18 （仅 64 位 zSeries）
10	Linux (32-bit) Linux x86	7 - Oracle 11g 及更高版本，须要 Patch 13104881 10 11, 13 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 414043.1
11	Linux IA (64-bit) Linux Itanium	10 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 414043.1 11 13 - Oracle 10g 及更高版本 7 - Oracle 11g 及更高版本，请参阅技术支持文档 Note: 414043.1，还须要 Patch 13104881 8, 12 - Oracle 11g 及更高版本，须要 Patch 13104881
12	Microsoft Windows 64-bit for AMD Microsoft Windows (x86-64)	7 - Oracle 10g 及更高版本，请参阅技术支持说明 Note: 414043.1 8 - Oracle 10g 及更高版本 12 11, 13 - Oracle 11g 及更高版本，须要 Patch 13104881
13	Linux 64-bit for AMD Linux x86-64	7 - Oracle 11g 及更高版本，请参阅技术支持文档 Note: 414043.1，还须要 Patch 13104881 10 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 414043.1 11 - Oracle 10g 及更高版本 8, 12 - Oracle 11g 及更高版本，须要 Patch 13104881 13 20 - Oracle 11g 及更高版本
15	HP Open VMS HP OpenVMS Alpha HP IA OpenVMS OpenVMS Itanium	15
16	Apple Mac OS Mac OS X Server	16
17	Solaris Operating System (x86) Solaris Operating System (x86)	17 20 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 414043.1
18	IBM Power Based Linux Linux on Power	9（仅 64 位 zSeries） 18
20	Solaris Operating System (AMD64) Solaris Operating System (x86-64)	13 - Oracle 11g 及更高版本 17 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 414043.1 20

3. 其余信息：

临时逻辑数据库滚动升级：    从 Oracle Database 11.1.0.7 开始，能够利用物理备用数据库，进行临时逻辑备库滚动数据库升级过程，将数据库滚动升级到新的 Oracle Patch Set（补丁程序集）和数据库发行版。请参阅“Maximum Availability Architecture Best Practice”一文中的 " Rolling Database Upgrades for Physical Standby Databases using Transient Logical Standby 11g "。使用数据库滚动升级过程使得备用数据库能够应用主数据库发送的重作，虽然主数据库仍然在旧的 Oracle 发行版或 patchset（补丁程序集）上运行。临时逻辑备库滚动升级过程要求，在升级前 Oracle 发行版部署到 Data Guard 配置中时，主平台和备用平台组合是重作日志应用（参见上表）和 SQL 应用（参阅技术支持文档 1085687.1）支持的配置。

包括物理和逻辑备用数据库组合的 Data Guard 配置：    Data Guard 配置包括一个主数据库和最多30个备用数据库。这些备用数据库能够是物理备用数据库和逻辑备用数据库的混合。单个Data Guard 配置中的全部物理备用数据库必须符合本说明中的要求。与此相似，若是配置包括逻辑备用数据库，则必须符合技术支持文档1085687.1 的要求。

Real Application Cluster 和 Automatic Storage Management:   主数据库和备用数据库没必要都是 Oracle RAC 数据库，也没必要均使用 ASM。例如，主数据库能够运行 Oracle RAC，使用或不使用 ASM，而备用数据库则能够是单实例，使用或不使用ASM。此外，在主数据库和备用数据库均为 Oracle RAC 数据库时，主数据库和备用数据库之间的 Oracle RAC节点数能够不一样。此外，主系统与备用系统之间的 ASM 和 CRS 的版本没必要相同。

Exadata Database Machine:        只要相同 Data Guard 配置中的主系统和备用系统的平台 ID 遵照上表中定义的支持要求，则主和/或备用数据库是驻留在 Exadata Database Machine 上仍是其余硬件上对于 Data Guard 来讲是透明的。若是使用了 Exadata Hybrid Columnar Compression (EHCC)，则强烈建议主系统和备用系统驻留在 Exadata 上。请参阅“Maximum Availability Architecture Best Practice”一文中的 " Disaster Recovery for Exadata Database Machine "。

参考

BUG:13104881   - ORA-600 [6101] DATA CORRUPTION IN 11.2.0.2 WINDOWS TO LINUX STANDBY DUPLICATION
NOTE:1079563.1   - RMAN DUPLICATE/RESTORE/RECOVER Mixed Platform Support
NOTE:414043.1   - Role Transitions for Data Guard Configurations Using Mixed Oracle Binaries
BUG:12702521   - CANNOT SUPPORT SPARC<->AIX MIXED DATA GUARD DUE TO CONTROLFILE INCOMPATIBILITY
BUG:13104881   - ORA-600 [6101] DATA CORRUPTION IN 11.2.0.2 WINDOWS TO LINUX STANDBY DUPLICATION

在物理 Data Guard 中对异构主备系统的支持 (文档 ID 1602437.1)

Data Guard中主数据库与物理备用数据库（Redo Apply）之间能够有什么差异？

本说明针对重作应用和 Oracle Data Guard 12 发行版 1 进行了更新。它适用于 Oracle Database 10g 和 Oracle Database 12c 的全部版本。

您是否但愿与其余 Oracle 客户、Oracle 员工和业内专家进一步探讨此主题？

您能够直接在本说明底部关于本文的讨论帖子中讨论本说明，介绍您的经验，也能够直接提出相关问题。

若是您但愿就其余文章和话题进行讨论，或者展开新的讨论，您能够访问中文数据库社区。

有关使用逻辑备用数据库（SQL Apply）的支持配置信息，请参阅技术支持Note 1085687.1

范围和适用性：

1. 肯定主数据库和备用数据库的平台 ID。

硬件生产商（例如 Dell 和 Sun 或 Hitachi 和 EMC）
硬件配置（例如，CPU 数、RAM 大小、存储配置等）
处理器（例如 x86-64 AMD64 和 x86-64 Intel 64；POWER4 和 POWER5）
操做系统发行版（例如 Red Hat Linux、SUSE Linux 或 Oracle Enterprise Linux）
O操做系统版本（例如 Windows 2000 和 Windows XP）

2. 若是您的主平台与备用平台的平台 ID 不一样，请检查下表以查看 Data Guard 重作日志应用（物理备用）是否支持您的配置。

表注释

在 Data Guard 11g 以前，Data Guard Broker在相同 Data Guard 配置中不支持不一样的字长，于是须要从 SQL*Plus 命令行管理混合字长的 Data Guard 配置。从 Data Guard 11g 开始消除了此限制。
主数据库和备用数据库必须设置为与下表中最低发行版（若是指定）相同的兼容性模式。
在任何环境中，若是主数据库和备用数据库之间存在与二进制级别相关的 PL/SQL 不兼容，则备用数据库没法以只读模式打开。下表中引用了文档 Note:414043.1，介绍这种状况的任意平台组合（该说明提供有关在角色转换后消除不兼容性的指导）。在 Oracle Database 11g 的这种环境中，能够经过将其临时转换为 Snapshot（快照）备用备用数据库来的方式来访问备用数据库，而在 Oracle Database 10g 中，则按照《Data Guard 10g Concepts and Administration guide》中的如下章节所述来以读/写方式打开备用数据库：Using a Physical Standby Database for Read/Write Testing and Reporting。这两种方法须要遵照 Note:414043.1 中的步骤操做才能使数据库对用户可用。
请确保阅读了下表中引用的技术支持文档。.
对于所支持平台组合，RMAN 一般支持物理备用数据库的实例化。有关详细信息，请参阅技术支持 Note 1079563.1。
支持组合中的平台可以以主或备用的角色运行。
在具备不一样 PLATFORM_ID 的任意配置中，Enterprise Manager 不能用于备用数据库建立或其余管理功能。Oracle 建议使用 Data Guard Broker命令行界面 (DGMGRL) 来管理 Oracle Database 11g 及更高版本的混合平台组合，Oracle Database 11g 以前的配置则使用 SQL*Plus 命令行界面。

PLATFORM_ID	PLATFORM_NAME 发行版名称	使用 Data Guard 重作日志应用（物理备用）时，相同 Data Guard 配置中支持的 PLATFORM_ID
2	Solaris[tm] OE (64-bit) Solaris Operating System (SPARC) (64-bit)	2 6 - 请参考文档 Note: 1982638.1 和 Note: 414043.1
3	HP-UX (64-bit) HP-UX PA-RISC	3 4 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 395982.1 和 Note:414043.1
4	HP-UX IA (64-bit) HP-UX Itanium	4 3 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 395982.1 和 Note:414043.1
5	HP Tru64 UNIX HP Tru64 UNIX	5
6	IBM AIX on POWER Systems (64-bit)	2 - 请参考文档 Note: 1982638.1 和 Note: 414043.1 6
7	Microsoft Windows (32-bit) Microsoft Windows (x86)	7 8, 12 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 414043.1 10 - Oracle 11g 及更高版本，须要 Patch 13104881 11, 13 - Oracle 11g 及更高版本，请参阅技术支持文档 Note: 414043.1，还须要 Patch 13104881
8	Microsoft Windows IA (64-bit) Microsoft Windows (64-bit Itanium)	7 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 414043.1 8 12 - Oracle 10g 及更高版本 11, 13 - Oracle 11g 及更高版本，须要 Patch 13104881
9	IBM zSeries Based Linux z/Linux	9 18 （仅 64 位 zSeries）
10	Linux (32-bit) Linux x86	7 - Oracle 11g 及更高版本，须要 Patch 13104881 10 11, 13 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 414043.1
11	Linux IA (64-bit) Linux Itanium	10 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 414043.1 11 13 - Oracle 10g 及更高版本 7 - Oracle 11g 及更高版本，请参阅技术支持文档 Note: 414043.1，还须要 Patch 13104881 8, 12 - Oracle 11g 及更高版本，须要 Patch 13104881
12	Microsoft Windows 64-bit for AMD Microsoft Windows (x86-64)	7 - Oracle 10g 及更高版本，请参阅技术支持说明 Note: 414043.1 8 - Oracle 10g 及更高版本 12 11, 13 - Oracle 11g 及更高版本，须要 Patch 13104881
13	Linux 64-bit for AMD Linux x86-64	7 - Oracle 11g 及更高版本，请参阅技术支持文档 Note: 414043.1，还须要 Patch 13104881 10 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 414043.1 11 - Oracle 10g 及更高版本 8, 12 - Oracle 11g 及更高版本，须要 Patch 13104881 13 20 - Oracle 11g 及更高版本
15	HP Open VMS HP OpenVMS Alpha HP IA OpenVMS OpenVMS Itanium	15
16	Apple Mac OS Mac OS X Server	16
17	Solaris Operating System (x86) Solaris Operating System (x86)	17 20 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 414043.1
18	IBM Power Based Linux Linux on Power	9（仅 64 位 zSeries） 18
20	Solaris Operating System (AMD64) Solaris Operating System (x86-64)	13 - Oracle 11g 及更高版本 17 - Oracle 10g 及更高版本，请参阅技术支持文档 Note: 414043.1 20

3. 其余信息：

临时逻辑数据库滚动升级：从 Oracle Database 11.1.0.7 开始，能够利用物理备用数据库，进行临时逻辑备库滚动数据库升级过程，将数据库滚动升级到新的 Oracle Patch Set（补丁程序集）和数据库发行版。请参阅“Maximum Availability Architecture Best Practice”一文中的 " Rolling Database Upgrades for Physical Standby Databases using Transient Logical Standby 11g "。使用数据库滚动升级过程使得备用数据库能够应用主数据库发送的重作，虽然主数据库仍然在旧的 Oracle 发行版或 patchset（补丁程序集）上运行。临时逻辑备库滚动升级过程要求，在升级前 Oracle 发行版部署到 Data Guard 配置中时，主平台和备用平台组合是重作日志应用（参见上表）和 SQL 应用（参阅技术支持文档 1085687.1）支持的配置。

包括物理和逻辑备用数据库组合的 Data Guard 配置： Data Guard 配置包括一个主数据库和最多30个备用数据库。这些备用数据库能够是物理备用数据库和逻辑备用数据库的混合。单个Data Guard 配置中的全部物理备用数据库必须符合本说明中的要求。与此相似，若是配置包括逻辑备用数据库，则必须符合技术支持文档1085687.1 的要求。

Real Application Cluster 和 Automatic Storage Management: 主数据库和备用数据库没必要都是 Oracle RAC 数据库，也没必要均使用 ASM。例如，主数据库能够运行 Oracle RAC，使用或不使用 ASM，而备用数据库则能够是单实例，使用或不使用ASM。此外，在主数据库和备用数据库均为 Oracle RAC 数据库时，主数据库和备用数据库之间的 Oracle RAC节点数能够不一样。此外，主系统与备用系统之间的 ASM 和 CRS 的版本没必要相同。

Exadata Database Machine: 只要相同 Data Guard 配置中的主系统和备用系统的平台 ID 遵照上表中定义的支持要求，则主和/或备用数据库是驻留在 Exadata Database Machine 上仍是其余硬件上对于 Data Guard 来讲是透明的。若是使用了 Exadata Hybrid Columnar Compression (EHCC)，则强烈建议主系统和备用系统驻留在 Exadata 上。请参阅“Maximum Availability Architecture Best Practice”一文中的 " Disaster Recovery for Exadata Database Machine "。

参考

BUG:13104881 - ORA-600 [6101] DATA CORRUPTION IN 11.2.0.2 WINDOWS TO LINUX STANDBY DUPLICATION NOTE:1079563.1 - RMAN DUPLICATE/RESTORE/RECOVER Mixed Platform Support NOTE:414043.1 - Role Transitions for Data Guard Configurations Using Mixed Oracle Binaries BUG:12702521 - CANNOT SUPPORT SPARC<->AIX MIXED DATA GUARD DUE TO CONTROLFILE INCOMPATIBILITY BUG:13104881 - ORA-600 [6101] DATA CORRUPTION IN 11.2.0.2 WINDOWS TO LINUX STANDBY DUPLICATION