DataGuard与异构平台

DataGuard对主备库异构平台的支持一直是让很多人纠结的问题,我们在学习Oracle数据卫士时必要优先阅读的官方文档是<Oracle Data Guard Concepts and Administration 10g Release 2>,在这个文档中给出了极为苛刻的硬件环境限制条件:

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.

以上主要提出了2点要求:即平台(platform)和字长(word size)都必须一致,注意这里不管是physical standby还是logical standby都要求遵守。

官方文档这样撰写的原因是Oracle并不推荐用户在异构平台上搭建DataGuard,如果有用户大量地部署异构平台上的DataGuard可能给后续的服务和支持带来麻烦;所以除非是找不到其他可用的硬件了,否则不推荐采用异构平台搭建的DataGuard环境来提供高可用性。

实际情况是在10g中已经有少数几个异构平台组合可以兼容physical standby或logical standby,而在11g中更增加了对physical standby支持的几种异构平台组合(As of Oracle Database 11g Data Guard provides increased flexibility for Data Guard configurations in which the primary and standby systems may have different CPU architectures, operating systems (for example, Windows & Linux), operating system binaries (32-bit/64-bit), or Oracle database binaries (32-bit/64-bit). For specific information about mixed-platform support, see the My Oracle Support note 413484.1)。

具体10g/11g DataGuard可以利用的异构平台组合,见下列图表:

10g
Physical Standby Logical Standby
Heterogeneous
Support
No Win<->Linux Only
Different
Word-size
(32 / 64 bit)
Win32<->Win64
Linux32<->Linux64
Win32->Win64  

Linux32->Linux64 (1 way only)

Heterogeneous AND Word-size No No

 

11g
Physical Standby Logical Standby
Heterogeneous
Support
Win<–>Linux
Solaris <–>AIX
Solaris<–>Linux
Win<->Linux Only
Different
Word-size
(32 / 64 bit)
Win32<->Win64
Linux32<->Linux64
Win32->Win64 Linux32->Linux64 (1 way only)
Heterogeneous AND Word-size Win32<->Linux64 Win32->Linux64
(1 way only)

 

而在metalink文档<Data Guard Support for Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration [ID 413484.1]><Data Guard Support for Heterogeneous Primary and Logical Standbys in Same Data Guard Configuration [ID 1085687.1]>中列出了更为详尽的平台间的兼容信息,在这里一并引用:

Physical Standbys

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

  1. 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.
  2. Both primary and standby databases must be set at the same compatibility mode as the minimum release (if specified) in the table below.
  3. 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.
  4. Please be sure to read Support Notes when referenced in the table below.
  5. RMAN generally supports instantiation of a physical standby database for the supported platform combinations. Please see Support Note 1079563.1 for details.
  6. Platforms in a supported combination may operate in either the primary or standby role.
  7. 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)
2 Solaris[tm] OE (64-bit)
Solaris Operating System (SPARC) (64-bit)
2
6 – Oracle 11.2.0.2 onward, primary database must be non-RAC and non-TDE
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 – Oracle 11.2.0.2 onward, primary database must be non-RAC and non-TDE
6
7 Microsoft Windows (32-bit)
Microsoft Windows (x86)
7
8, 12  – Oracle 10g onward, see Support Note 414043.1
10 – Oracle 11g onward
11, 13 – Oracle 11g onward, see Support Note 414043.1
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
9 IBM zSeries Based Linux
z/Linux
9
18 (64-bit zSeries only)
10 Linux (32-bit)
Linux x86
7 – Oracle 11g onward
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
8, 12 – Oracle 11g onward
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
13 Linux 64-bit for AMD
Linux x86-64
7 – Oracle 11g onward, see Support Note 414043.1
10 – Oracle 10g onward, see Support Note 414043.1
11 – Oracle 10g onward
8, 12 – Oracle 11g onward
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

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

  1. All mixed platform combinations for 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 Data Guard configuration, thus requiring all management from the SQL*Plus command line.  This restriction is lifted from Data Guard 11g onward.
  3. Both primary and standby databases must be set at the same compatibility mode as the minimum release (if specified) in the table below.
  4. Please be sure to read Support Notes when referenced in the table below.
  5. RMAN generally supports instantiation of a physical standby database for the supported platform combinations. Please see Support Note 1079563.1 for details.
  6. Platforms in a supported combination may operate in either the primary or standby role unless otherwise specified.
  7. 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
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

Reference:

<Cross Platform Database Migrations>-Owen Ireland

<Data Guard Support for Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration [ID 413484.1]>

<Data Guard Support for Heterogeneous Primary and Logical Standbys in Same Data Guard Configuration [ID 1085687.1]>



关注dbDao.com的新浪微博

扫码关注dbDao.com 微信公众号:

Comments

  1. Role Transitions for Data Guard Configurations Using Mixed Oracle Binaries [ID 414043.1]

    Summary

    Beginning with Oracle Database 10g, there are certain configurations where Data Guard Redo Apply (physical standby) can support different Oracle binaries between primary and standby databases as long as all systems in the Data Guard configuration are running the same OS family. For example, you may have a primary database with 32bit Oracle binaries on Red Hat 32bit, and a physical standby database with 64bit Oracle binaries on Red Hat 64bit. Such configurations must follow additional procedures during Data Guard role transitions (switchover and failover) as described in this MetaLink note, below. If these procedures are not followed then errors will occur when trying to open the new primary database. One example error sequence would be:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-06553: PLS-801: internal error [56327]

    \
    For additional information on how Data Guard supports configurations in which the primary database/system may not be identical to its standby database(s)/system(s), please see MetaLink Note 413484.1

    Restrictions
    SQL Apply (logical standby) always requires that the bit-ness of the Oracle Database is identical on all systems in a Data Guard configuration. Continuing with the example provided in the summary above of a Red Hat 32bit/64bit primary/standby, if you are using SQL Apply you must use 32 bit Oracle binaries on both primary and standby.
    The bit-ness of the Oracle database must be identical if you are using any Oracle release before Oracle Database 10g for both SQL Apply and Redo Apply. Continuing with the example provided in the summary above of a Red Hat 32bit/64bit primary/standby, if you are using Oracle9i you must use 32 bit Oracle binaries on both primary and standby (either physical or logical standby).
    The Data Guard Broker does not support different binaries in the same Data Guard configuration in Oracle Database 10g. All such configurations must be managed from the SQL*Plus command line. Beginning with Data Guard 11g onward, this restriction is lifted and the Data Guard Broker does support Oracle 11g databases of mixed word-size in the same Data Guard configuration.
    Data Guard Fast-start Failover will failover in a mixed Oracle binary configuration but it will be unable to open the new primary database until the procedure below is followed.

    Additional Role Transition Procedures when using mixed Oracle binaries:

    If you are running a physical standby configuration where the primary and standby have different Oracle binaries you will need to follow the instructions below on the new primary as part of any Data Guard role transition (switchover or failover) after a standby becomes a primary database (supported configurations are defined in MetaLink Note 413484.1). This procedure is necessary when transitioning roles in either direction.

    Note: If you are using Oracle OLAP then you must also follow MetaLink Note 352306.1 . Additionally, as a precaution for a failover, you may want to backup/export the user-created AW’s ahead of time and periodically.

    1. Shutdown the new primary database
    If using RAC then set database to unclustered: SQL> alter system set cluster_database=false scope=spfile;
    SQL> shutdown immediate

    2. Startup the new primary in UPGRADE mode
    SQL> startup upgrade

    3. Invalidate existing PL/SQL modules in preparation to convert the format required by the new primary. Note that there should be no other DDL on the database while running the script. Not following thisrecommendation may lead to deadlocks.
    SQL> spool utlirp.log
    SQL> @?/rdbms/admin/utlirp
    SQL> spool off

    4. Restart the database
    If using RAC then set database back to clustered:
    SQL> alter system set cluster_database=true scope=spfile;
    SQL> shutdown immediate
    SQL> startup

    5. Recompile all invalid PL/SQL modules to be in the format required by the new primary database.
    SQL> spool utlrp.log
    SQL> @?/rdbms/admin/utlrp
    SQL> spool off

    6. Verify that all expected packages and classes are valid.
    SQL> SELECT count(*) FROM dba_objects WHERE status=’INVALID’;
    SQL> SELECT distinct object_name FROM dba_objects WHERE status=’INVALID’;

  2. Solaris AIX 和 SolarisLinux
    1. 第一个Solaris应该是SPARC平台,第二个Solaris应该只是x86-64平台
    2. 你确认这两个异构环境的物理standby在10g的时候就被支持了?

  3. admin says:

    10g Summary – Heterogenous Logical Standby always requires that the Word-size of the Oracle Database is identical on all systems in a Data Guard configuration.

    Physical Standby can’t do heterogenous until 11g, but can do different bitness on database on same platform

    1-WAY: 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. There are exceptions to this table though.

  4. 在物理 Data Guard 中对异构主备系统的支持 (Doc 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_IDPLATFORM_NAME发行版名称使用 Data Guard 重做日志应用(物理备用)时,相同 Data Guard 配置中支持的 PLATFORM_ID2Solaris[tm] OE (64-bit)Solaris Operating System (SPARC) (64-bit) 26 – 由于 Bug 12702521 中报告的问题,不支持此项3 HP-UX (64-bit)HP-UX PA-RISC 34 – Oracle 10g 及更高版本,请参阅技术支持文档 Note: 395982.1 和 Note:414043.14 HP-UX IA (64-bit)HP-UX Itanium 43 – Oracle 10g 及更高版本,请参阅技术支持文档 Note: 395982.1 和 Note:414043.15 HP Tru64 UNIXHP Tru64 UNIX 56 IBM AIX on POWER Systems (64-bit)2 – 由于 Bug 12702521 中报告的问题,不支持此项67 Microsoft Windows (32-bit)Microsoft Windows (x86)78, 12 – Oracle 10g 及更高版本,请参阅 技术支持文档 Note: 414043.1 10 – Oracle 11g 及更高版本,需要 Patch 1310488111, 13 – Oracle 11g 及更高版本,请参阅 技术支持文档 Note: 414043.1,还需要 Patch 131048818 Microsoft Windows IA (64-bit)Microsoft Windows (64-bit Itanium) 7 – Oracle 10g 及更高版本,请参阅 技术支持文档 Note: 414043.1812 – Oracle 10g 及更高版本11, 13 – Oracle 11g 及更高版本,需要 Patch 131048819 IBM zSeries Based Linuxz/Linux 918 (仅 64 位 zSeries)10 Linux (32-bit)Linux x86 7 – Oracle 11g 及更高版本,需要 Patch 13104881 1011, 13 – Oracle 10g 及更高版本,请参阅 技术支持文档 Note: 414043.111 Linux IA (64-bit)Linux Itanium 10 – Oracle 10g 及更高版本,请参阅 技术支持文档 Note: 414043.11113 – Oracle 10g 及更高版本7 – Oracle 11g 及更高版本,请参阅 技术支持文档 Note: 414043.1,还需要 Patch 131048818, 12 – Oracle 11g 及更高版本,需要 Patch 1310488112 Microsoft Windows 64-bit for AMDMicrosoft Windows (x86-64) 7 – Oracle 10g 及更高版本,请参阅技术支持说明 Note: 414043.18 – Oracle 10g 及更高版本1211, 13 – Oracle 11g 及更高版本,需要 Patch 1310488113 Linux 64-bit for AMDLinux x86-64 7 – Oracle 11g 及更高版本,请参阅 技术支持文档 Note: 414043.1,还需要 Patch 1310488110 – Oracle 10g 及更高版本,请参阅技术支持文档 Note: 414043.111 – Oracle 10g 及更高版本8, 12 – Oracle 11g 及更高版本,需要 Patch 131048811320 – Oracle 11g 及更高版本15 HP Open VMSHP OpenVMS AlphaHP IA OpenVMSOpenVMS Itanium 1516 Apple Mac OSMac OS X Server 1617 Solaris Operating System (x86)Solaris Operating System (x86) 1720 – Oracle 10g 及更高版本,请参阅 技术支持文档 Note: 414043.118 IBM Power Based LinuxLinux on Power 9(仅 64 位 zSeries)1820 Solaris Operating System (AMD64)Solaris Operating System (x86-64) 13 – Oracle 11g 及更高版本17 – Oracle 10g 及更高版本,请参阅 技术支持文档 Note: 414043.1203. 其他信息:临时逻辑数据库滚动升级: 从 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”。

Speak Your Mind

TEL/電話+86 13764045638
Email service@parnassusdata.com
QQ 47079569