一：请描述Oracle Data Guard优点有哪些;
二：请描述DG备库类型和特点;
三：请描述如何将物理备用数据库转换为快照备用数据库;
四：请描述如何将快照备用数据库转换为物理备用数据库;
五：请描述DG环境需要配置哪些参数;
六：请描述如果DG备库服务器要回收，如何关闭DG同步关系;
七：请描述在DG执行SWITCHOVER前需要注意什么;
八：请描述在DG主、备库都是二节点RAC的场景下，执行SWITCHOVER的过程;
九：请描述Oracle DG FAILOVER过程;
十：请描述Oracle DG GAP问题处理方法;
十一：请描述Oracle DG有哪些进程;
十二：请描述Oracle DG常用命令。

一：请描述Oracle Data Guard优点有哪些;

二：请描述DG备库类型和特点;

三：请描述如何将物理备用数据库转换为快照备用数据库;

四：请描述如何将快照备用数据库转换为物理备用数据库;

五：请描述DG环境需要配置哪些参数;

六：请描述如果DG备库服务器要回收，如何关闭DG同步关系;

七：请描述在DG执行SWITCHOVER前需要注意什么;

八：请描述在DG主、备库都是二节点RAC的场景下，执行SWITCHOVER的过程;

九：请描述Oracle DG FAILOVER过程;

十：请描述Oracle DG GAP问题处理方法;

十一：请描述Oracle DG有哪些进程;

十二：请描述Oracle DG常用命令。

一：请描述Oracle Data Guard优点有哪些

Summary of Oracle Data Guard Benefits
Oracle Data Guard提供了一个高效、全面的灾难恢复和高可用性解决方案。
Oracle Data Guard provides an efficient and comprehensive disaster recovery and high availability solution.

Summary of Oracle Data Guard Benefits

Oracle Data Guard提供了一个高效、全面的灾难恢复和高可用性解决方案。

Oracle Data Guard provides an efficient and comprehensive disaster recovery and high availability solution.

Oracle Data Guard提供以下好处：

Oracle Data Guard offers these benefits:

1.高可用性

High availability
Oracle Data Guard易于管理的switchover和failover功能允许在主数据库和备用数据库之间进行角色转换，从而最大限度地减少主数据库在计划内和计划外停机时的停机时间。
Oracle Data Guard’s easy-to-manage switchover and failover capabilities allow role reversals between primary and standby databases, minimizing the downtime of the primary database for planned and unplanned outages.

High availability

Oracle Data Guard易于管理的switchover和failover功能允许在主数据库和备用数据库之间进行角色转换，从而最大限度地减少主数据库在计划内和计划外停机时的停机时间。

Oracle Data Guard’s easy-to-manage switchover and failover capabilities allow role reversals between primary and standby databases, minimizing the downtime of the primary database for planned and unplanned outages.

2.完整的数据保护

Complete data protection
Oracle Data Guard可以确保零数据丢失，即使在遇到意外情况时也是如此。
Oracle Data Guard can ensure zero data loss, even in the face of unforeseendisasters. 
备用数据库可防止所有类型的计划外停机，包括数据损坏和管理错误。
A standby database provides a safeguard against unplanned outages of all types, including data corruption and administrative error. 
因为从主数据库接收的重做数据在备用数据库中进行验证，所以主数据库中可能发生的物理损坏不会传播到备用数据库。
Because the redo data received from a primary database is validated at a standby database, physical corruptions that can occur at a primary database are not propagated to the standby database. 
在备用数据库上执行的附加验证还可以防止逻辑块内损坏和丢失写入损坏传播到备用数据库。
Additional validation performed at a standby database also prevents logical intra-block corruptions and lost-write corruptions from propagating to the standby. 
类似地，管理错误（如存储管理员意外删除文件）不会传播到备用数据库。
Similarly, administrative errors such as accidental file deletions by a storage administrator are not propagated to a standby database. 
物理备用数据库也可用于防止用户错误，方法是延迟重做应用，或使用闪回数据库倒回备用数据库并提取数据的良好副本。
A physical standby database can also be used to protect against user errors either by delaying the redo apply or by using Flashback Database to rewind the standby and extract a good copy of the data.

Complete data protection

Oracle Data Guard可以确保零数据丢失，即使在遇到意外情况时也是如此。

Oracle Data Guard can ensure zero data loss, even in the face of unforeseendisasters.

备用数据库可防止所有类型的计划外停机，包括数据损坏和管理错误。

A standby database provides a safeguard against unplanned outages of all types, including data corruption and administrative error.

因为从主数据库接收的重做数据在备用数据库中进行验证，所以主数据库中可能发生的物理损坏不会传播到备用数据库。

Because the redo data received from a primary database is validated at a standby database, physical corruptions that can occur at a primary database are not propagated to the standby database.

在备用数据库上执行的附加验证还可以防止逻辑块内损坏和丢失写入损坏传播到备用数据库。

Additional validation performed at a standby database also prevents logical intra-block corruptions and lost-write corruptions from propagating to the standby.

类似地，管理错误（如存储管理员意外删除文件）不会传播到备用数据库。

Similarly, administrative errors such as accidental file deletions by a storage administrator are not propagated to a standby database.

物理备用数据库也可用于防止用户错误，方法是延迟重做应用，或使用闪回数据库倒回备用数据库并提取数据的良好副本。

A physical standby database can also be used to protect against user errors either by delaying the redo apply or by using Flashback Database to rewind the standby and extract a good copy of the data.

3.有效利用系统资源

Efficient use of system resources
使用从主数据库接收的重做数据更新的备用数据库表可用于其他任务，如备份、报告、汇总和查询，从而减少执行这些任务所需的主数据库工作负载，节省宝贵的CPU和I/O周期。
The standby database tables that are updated with redo data received from the primary database can be used for other tasks such as backups, reporting,summations, and queries, thereby reducing the primary database workloadnecessary to perform these tasks, saving valuable CPU and I/O cycles.

Efficient use of system resources

使用从主数据库接收的重做数据更新的备用数据库表可用于其他任务，如备份、报告、汇总和查询，从而减少执行这些任务所需的主数据库工作负载，节省宝贵的CPU和I/O周期。

The standby database tables that are updated with redo data received from the primary database can be used for other tasks such as backups, reporting,summations, and queries, thereby reducing the primary database workloadnecessary to perform these tasks, saving valuable CPU and I/O cycles.

4.数据保护的灵活性，以平衡可用性和性能要求

Flexibility in data protection to balance availability against performance requirements
Oracle Data Guard提供了最大保护、最大可用性和最大性能模式，帮助企业平衡数据可用性和系统性能需求。
Oracle Data Guard offers maximum protection, maximum availability, and maximum performance modes to help enterprises balance data availability against system performance requirements.

Flexibility in data protection to balance availability against performance requirements

Oracle Data Guard提供了最大保护、最大可用性和最大性能模式，帮助企业平衡数据可用性和系统性能需求。

Oracle Data Guard offers maximum protection, maximum availability, and maximum performance modes to help enterprises balance data availability against system performance requirements.

5.自动gap检测和解决

Automatic gap detection and resolution
如果主数据库和一个或多个备用数据库之间的连接丢失（例如，由于网络问题），
If connectivity is lost between the primary and one or more standby databases (for example, due to network problems), 
这样，在主数据库上生成的重做数据就不能发送到那些备用数据库。
then redo data being generated on the primary database cannot be sent to those standby databases. 
重新建立连接后，Oracle Data Guard会自动检测到丢失的存档重做日志文件（称为gap），然后将丢失的存档重做日志文件自动传输到备用数据库。
After a connection is reestablished, the missing archived redo log files (referred to as a gap) are automatically detected by Oracle Data Guard, which then automatically transmits the missing archived redo log files to the standby databases. 
备用数据库与主数据库同步，无需DBA手动干预。
The standby databases are synchronized with the primary database, without manual intervention by the DBA.

Automatic gap detection and resolution

如果主数据库和一个或多个备用数据库之间的连接丢失（例如，由于网络问题），

If connectivity is lost between the primary and one or more standby databases (for example, due to network problems),

这样，在主数据库上生成的重做数据就不能发送到那些备用数据库。

then redo data being generated on the primary database cannot be sent to those standby databases.

重新建立连接后，Oracle Data Guard会自动检测到丢失的存档重做日志文件（称为gap），然后将丢失的存档重做日志文件自动传输到备用数据库。

After a connection is reestablished, the missing archived redo log files (referred to as a gap) are automatically detected by Oracle Data Guard, which then automatically transmits the missing archived redo log files to the standby databases.

备用数据库与主数据库同步，无需DBA手动干预。

The standby databases are synchronized with the primary database, without manual intervention by the DBA.

6.集中化、简单化管理

Centralized and simple management
Oracle Data Guard broker提供了图形用户界面和命令行界面，用于在DG配置中跨多个数据库自动化管理和操作任务。
代理还监视单个Oracle Data Guard配置中的所有系统。
The Oracle Data Guard broker provides a graphical user interface and a command-line interface to automate management and operational tasks across multiple databases in an Oracle Data Guard configuration. 
The broker also monitors all of the systems within a single Oracle Data Guard configuration.

Centralized and simple management

Oracle Data Guard broker提供了图形用户界面和命令行界面，用于在DG配置中跨多个数据库自动化管理和操作任务。

代理还监视单个Oracle Data Guard配置中的所有系统。

The Oracle Data Guard broker provides a graphical user interface and a command-line interface to automate management and operational tasks across multiple databases in an Oracle Data Guard configuration.

The broker also monitors all of the systems within a single Oracle Data Guard configuration.

7.与Oracle数据库集成

Integration with Oracle Database
Oracle Data Guard是Oracle Database Enterprise Edition的一项功能，不需要单独安装。
Oracle Data Guard is a feature of Oracle Database Enterprise Edition and does not require separate installation.

Integration with Oracle Database

Oracle Data Guard是Oracle Database Enterprise Edition的一项功能，不需要单独安装。

Oracle Data Guard is a feature of Oracle Database Enterprise Edition and does not require separate installation.

8.自动角色转换

Automatic role transitions
启用快速启动故障切换后，如果主站点发生灾难，Oracle Data Guard broker将自动故障切换到同步备用站点，而无需DBA干预。此外，应用程序会自动通知角色转换。
When fast-start failover is enabled, the Oracle Data Guard broker automatically fails over to a synchronized standby site in the event of a disaster at the primary site, requiring no intervention by the DBA. In addition, applications are automatically notified of the role transition.

Automatic role transitions

启用快速启动故障切换后，如果主站点发生灾难，Oracle Data Guard broker将自动故障切换到同步备用站点，而无需DBA干预。此外，应用程序会自动通知角色转换。

When fast-start failover is enabled, the Oracle Data Guard broker automatically fails over to a synchronized standby site in the event of a disaster at the primary site, requiring no intervention by the DBA. In addition, applications are automatically notified of the role transition.

二：请描述DG备库类型和特点

Standby Database Types
备用数据库是Oracle生产数据库的事务一致性副本，它最初是从主数据库的备份副本创建的。
A standby database is a transactionally consistent copy of an Oracle production database that is initially created from a backup copy of the primary database.
一旦创建并配置了备用数据库，Oracle Data Guard就会通过将主数据库redo数据传输到备用系统来自动维护备用数据库，并将redo数据应用到备用数据库。
Once the standby database is created and configured, Oracle Data Guard automatically maintains the standby database by transmitting primary database redo data to the standby system, where the redo data is applied to the standby database.

Standby Database Types

备用数据库是Oracle生产数据库的事务一致性副本，它最初是从主数据库的备份副本创建的。

A standby database is a transactionally consistent copy of an Oracle production database that is initially created from a backup copy of the primary database.

一旦创建并配置了备用数据库，Oracle Data Guard就会通过将主数据库redo数据传输到备用系统来自动维护备用数据库，并将redo数据应用到备用数据库。

Once the standby database is created and configured, Oracle Data Guard automatically maintains the standby database by transmitting primary database redo data to the standby system, where the redo data is applied to the standby database.

备用数据库可以是以下类型之一：物理备用数据库、逻辑备用数据库或快照备用数据库。

A standby database can be one of these types: a physical standby database, a logical standby database, or a snapshot standby database. 
如果需要，物理或逻辑备用数据库都可以充当主数据库的角色并接管生产处理。
If needed, either a physical or a logical standby database can assume the role of the primary database and take over production processing. 
Oracle Data Guard配置可以包括这些类型的备用数据库的任意组合。
An Oracle Data Guard configuration can include any combination of these types of standby databases.

A standby database can be one of these types: a physical standby database, a logical standby database, or a snapshot standby database.

如果需要，物理或逻辑备用数据库都可以充当主数据库的角色并接管生产处理。

If needed, either a physical or a logical standby database can assume the role of the primary database and take over production processing.

Oracle Data Guard配置可以包括这些类型的备用数据库的任意组合。

An Oracle Data Guard configuration can include any combination of these types of standby databases.

2.1 Physical Standby Databases

物理备用数据库是主数据库的精确逐块副本。
A physical standby database is an exact, block-for-block copy of a primary database.
物理备份通过一个称为Redo Apply的过程作为精确副本进行维护，在这个过程中，使用数据库恢复机制将从主数据库接收的Redo数据连续应用到物理备份数据库。
A physical standby is maintained as an exact copy through a process called Redo Apply, in which redo data received from a primary database is continuously applied to a physical standby database using the database recovery mechanisms.
可以打开物理备用数据库进行只读访问，并用于从主数据库卸载查询。
A physical standby database can be opened for read-only access and used to offload queries from a primary database. 
如果购买了Oracle Active Data Guard选项的许可证，那么Redo Apply可以在物理备用数据库打开时处于活动状态，从而允许查询返回与从主数据库返回的结果相同的结果。
If a license for the Oracle Active Data Guard option has been purchased, Redo Apply can be active while the physical standby database is open, thus allowing queries to return results that are identical to what would be returned from the primary database. 
此功能称为实时查询功能。
This capability is known as the real-time query feature.

物理备用数据库是主数据库的精确逐块副本。

A physical standby database is an exact, block-for-block copy of a primary database.

物理备份通过一个称为Redo Apply的过程作为精确副本进行维护，在这个过程中，使用数据库恢复机制将从主数据库接收的Redo数据连续应用到物理备份数据库。

A physical standby is maintained as an exact copy through a process called Redo Apply, in which redo data received from a primary database is continuously applied to a physical standby database using the database recovery mechanisms.

可以打开物理备用数据库进行只读访问，并用于从主数据库卸载查询。

A physical standby database can be opened for read-only access and used to offload queries from a primary database.

如果购买了Oracle Active Data Guard选项的许可证，那么Redo Apply可以在物理备用数据库打开时处于活动状态，从而允许查询返回与从主数据库返回的结果相同的结果。

If a license for the Oracle Active Data Guard option has been purchased, Redo Apply can be active while the physical standby database is open, thus allowing queries to return results that are identical to what would be returned from the primary database.

此功能称为实时查询功能。

This capability is known as the real-time query feature.

Physical Standby Database优点

Benefits of a Physical Standby Database
A physical standby database provides the following benefits:

1 2	Benefits of a Physical Standby Database A physical standby database provides the following benefits:

灾难恢复和高可用性

Disaster recovery and high availability
物理备用数据库是一种健壮、高效的灾难恢复和高可用性解决方案。
A physical standby database is a robust and efficient disaster recovery and high availability solution.
易于管理的切换和故障切换功能允许在主数据库和物理备用数据库之间轻松进行角色转换，从而最大限度地减少主数据库因计划内和计划外停机而导致的停机时间。
Easy-to-manage switchover and failover capabilities allow easy role reversals between primary and physical standby databases, minimizing the downtime of the primary database for planned and unplanned outages.

Disaster recovery and high availability

物理备用数据库是一种健壮、高效的灾难恢复和高可用性解决方案。

A physical standby database is a robust and efficient disaster recovery and high availability solution.

易于管理的切换和故障切换功能允许在主数据库和物理备用数据库之间轻松进行角色转换，从而最大限度地减少主数据库因计划内和计划外停机而导致的停机时间。

Easy-to-manage switchover and failover capabilities allow easy role reversals between primary and physical standby databases, minimizing the downtime of the primary database for planned and unplanned outages.

数据保护

Data protection
物理备用数据库可以防止数据丢失，即使是在遇到不可预见的灾难时。
A physical standby database can prevent data loss, even in the face of unforeseen disasters. 
物理备用数据库支持所有数据类型，以及主数据库可以支持的所有DDL和DML操作。
A physical standby database supports all datatypes, and all DDL and DML operations that the primary database can support.
它还提供了防止数据损坏和用户错误的保护措施。
It also provides a safeguard against data corruptions and user errors. 
主数据库上的存储级物理损坏不会传播到备用数据库。
Storage level physical corruptions on the primary database are not propagated to a standby database.
类似地，可以很容易地解决逻辑损坏或用户错误，否则会导致数据丢失。
Similarly, logical corruptions or user errors that would otherwise cause data loss can be easily resolved.

Data protection

物理备用数据库可以防止数据丢失，即使是在遇到不可预见的灾难时。

A physical standby database can prevent data loss, even in the face of unforeseen disasters.

物理备用数据库支持所有数据类型，以及主数据库可以支持的所有DDL和DML操作。

A physical standby database supports all datatypes, and all DDL and DML operations that the primary database can support.

它还提供了防止数据损坏和用户错误的保护措施。

It also provides a safeguard against data corruptions and user errors.

主数据库上的存储级物理损坏不会传播到备用数据库。

Storage level physical corruptions on the primary database are not propagated to a standby database.

类似地，可以很容易地解决逻辑损坏或用户错误，否则会导致数据丢失。

Similarly, logical corruptions or user errors that would otherwise cause data loss can be easily resolved.

减少主数据库工作负载

Reduction in primary database workload
Oracle Recovery Manager（RMAN）可以使用物理备用数据库从主数据库卸载备份，从而节省宝贵的CPU和I/O周期。
Oracle Recovery Manager (RMAN) can use a physical standby database to offload backups from a primary database, saving valuable CPU and I/O cycles.
当Redo Apply处于活动状态时，还可以查询物理备用数据库，这样可以将查询从主数据库卸载到物理备用数据库，从而进一步减少主数据库的工作负载。
A physical standby database can also be queried while Redo Apply is active, which allows queries to be offloaded from the primary to a physical standby, further reducing the primary workload.

Reduction in primary database workload

Oracle Recovery Manager（RMAN）可以使用物理备用数据库从主数据库卸载备份，从而节省宝贵的CPU和I/O周期。

Oracle Recovery Manager (RMAN) can use a physical standby database to offload backups from a primary database, saving valuable CPU and I/O cycles.

当Redo Apply处于活动状态时，还可以查询物理备用数据库，这样可以将查询从主数据库卸载到物理备用数据库，从而进一步减少主数据库的工作负载。

A physical standby database can also be queried while Redo Apply is active, which allows queries to be offloaded from the primary to a physical standby, further reducing the primary workload.

性能

Performance
物理备用数据库使用的Redo Apply技术是保持备用数据库更新为主数据库所做更改的最有效机制，因为它使用绕过所有SQL级代码层的低级恢复机制应用更改。
The Redo Apply technology used by a physical standby database is the most efficient mechanism for keeping a standby database updated with changes being made at a primary database because it applies changes using low-level recovery mechanisms which bypass all SQL level code layers.

Performance

物理备用数据库使用的Redo Apply技术是保持备用数据库更新为主数据库所做更改的最有效机制，因为它使用绕过所有SQL级代码层的低级恢复机制应用更改。

The Redo Apply technology used by a physical standby database is the most efficient mechanism for keeping a standby database updated with changes being made at a primary database because it applies changes using low-level recovery mechanisms which bypass all SQL level code layers.

2.2 Logical Standby Databases

逻辑备用数据库最初是作为主数据库的相同副本创建的，但以后可以更改为具有不同的结构。
A logical standby database is initially created as an identical copy of the primary database, but it later can be altered to have a different structure.
通过执行SQL语句更新逻辑备用数据库。
The logical standby database is updated by executing SQL statements. 
逻辑备用数据库的灵活性使您可以升级Oracle数据库软件（修补程序集和新的Oracle数据库版本），并以滚动方式执行其他数据库维护，几乎没有停机。
The flexibility of a logical standby database lets you upgrade Oracle Database software (patch sets and new Oracle Database releases) and perform other database maintenance in rolling fashion with almost no downtime. 
从Oracle Database 11g开始，临时逻辑数据库滚动升级过程也可以用于现有的物理备用数据库。
From Oracle Database 11g onward, the transient logical database rolling upgrade process can also be used with existing physical standby databases.
Oracle Data Guard通过将日志文件中的数据转换为SQL语句，然后在逻辑备用数据库上执行SQL语句，自动将归档的重做日志文件或备用重做日志文件中的信息应用到逻辑备用数据库。
Oracle Data Guard automatically applies information from the archived redo log file or standby redo log file to the logical standby database by transforming the data in the log files into SQL statements and then executing the SQL statements on the logical standby database. 
因为逻辑备用数据库是使用SQL语句更新的，所以它必须保持打开状态。
Because the logical standby database is updated using SQL statements, it must remain open. 
尽管逻辑备用数据库是以读/写模式打开的，但其重新生成的SQL的目标表仅可用于只读操作。
Although the logical standby database is opened in read/write mode, its target tables for the regenerated SQL are available only for read-only operations. 
在更新这些表时，它们可以同时用于其他任务，如报告、汇总和查询。
While those tables are being updated, they can be used simultaneously for other tasks such as reporting,summations, and queries.
逻辑备用数据库对数据类型、表类型以及DDL和DML操作类型有一些限制。
A logical standby database has some restrictions on data types, types of tables, and types of DDL and DML operations.
有关逻辑备用数据库上的数据类型和DDL支持的信息，请参见逻辑备用数据库上的数据类型和DDL支持。
See Data Type and DDL Support on a Logical Standby Database for information on data type and DDL support on logical standby databases.

逻辑备用数据库最初是作为主数据库的相同副本创建的，但以后可以更改为具有不同的结构。

A logical standby database is initially created as an identical copy of the primary database, but it later can be altered to have a different structure.

通过执行SQL语句更新逻辑备用数据库。

The logical standby database is updated by executing SQL statements.

逻辑备用数据库的灵活性使您可以升级Oracle数据库软件（修补程序集和新的Oracle数据库版本），并以滚动方式执行其他数据库维护，几乎没有停机。

The flexibility of a logical standby database lets you upgrade Oracle Database software (patch sets and new Oracle Database releases) and perform other database maintenance in rolling fashion with almost no downtime.

从Oracle Database 11g开始，临时逻辑数据库滚动升级过程也可以用于现有的物理备用数据库。

From Oracle Database 11g onward, the transient logical database rolling upgrade process can also be used with existing physical standby databases.

Oracle Data Guard通过将日志文件中的数据转换为SQL语句，然后在逻辑备用数据库上执行SQL语句，自动将归档的重做日志文件或备用重做日志文件中的信息应用到逻辑备用数据库。

Oracle Data Guard automatically applies information from the archived redo log file or standby redo log file to the logical standby database by transforming the data in the log files into SQL statements and then executing the SQL statements on the logical standby database.

因为逻辑备用数据库是使用SQL语句更新的，所以它必须保持打开状态。

Because the logical standby database is updated using SQL statements, it must remain open.

尽管逻辑备用数据库是以读/写模式打开的，但其重新生成的SQL的目标表仅可用于只读操作。

Although the logical standby database is opened in read/write mode, its target tables for the regenerated SQL are available only for read-only operations.

在更新这些表时，它们可以同时用于其他任务，如报告、汇总和查询。

While those tables are being updated, they can be used simultaneously for other tasks such as reporting,summations, and queries.

逻辑备用数据库对数据类型、表类型以及DDL和DML操作类型有一些限制。

A logical standby database has some restrictions on data types, types of tables, and types of DDL and DML operations.

有关逻辑备用数据库上的数据类型和DDL支持的信息，请参见逻辑备用数据库上的数据类型和DDL支持。

See Data Type and DDL Support on a Logical Standby Database for information on data type and DDL support on logical standby databases.

逻辑备用数据库的优点

Benefits of a Logical Standby Database
逻辑备用数据库是高可用性（HA）的理想选择，同时还能提供数据恢复（DR）好处。
A logical standby database is ideal for high availability (HA) while still offering data recovery (DR) benefits. 
与物理备用数据库相比，逻辑备用数据库提供了显著的附加HA好处：
Compared to a physical standby database, a logical standby database provides significant additional HA benefits:

Benefits of a Logical Standby Database

逻辑备用数据库是高可用性（HA）的理想选择，同时还能提供数据恢复（DR）好处。

A logical standby database is ideal for high availability (HA) while still offering data recovery (DR) benefits.

与物理备用数据库相比，逻辑备用数据库提供了显著的附加HA好处：

Compared to a physical standby database, a logical standby database provides significant additional HA benefits:

最大限度地减少软件升级的停机时间

• Minimizing downtime on software upgrades
逻辑备用数据库是以滚动方式升级Oracle Data Guard配置的理想选择。
A logical standby database is ideal for upgrading an Oracle Data Guard configuration in a rolling fashion. 
逻辑待机可用于大大减少与应用补丁集和新软件版本相关的停机时间。
Logical standby can be used to greatly reduce downtime associated with applying patchsets and new software releases. 
逻辑备用可以升级到新版本，然后切换为活动主版本。
A logical standby can be upgraded to the new release and then switched over to become the active primary. 
这允许在旧的主设备转换为逻辑备用设备并应用补丁集时实现完全可用性。
This allows full availability while the old primary is converted to a logical standby and the patchset is applied. 
逻辑备用程序为DBMS\u ROLLING PL/SQL包提供了底层平台，它提供的功能允许您在滚动升级和其他存储重组的上下文中使您的Oracle Data Guard配置高度可用。
Logical standbys provide the underlying platform for the DBMS_ROLLING PL/SQL package, which provides functionality that allows you to make your Oracle Data Guard configuration highly available in the context of rolling upgrades and other storage reorganization.

• Minimizing downtime on software upgrades

逻辑备用数据库是以滚动方式升级Oracle Data Guard配置的理想选择。

A logical standby database is ideal for upgrading an Oracle Data Guard configuration in a rolling fashion.

逻辑待机可用于大大减少与应用补丁集和新软件版本相关的停机时间。

Logical standby can be used to greatly reduce downtime associated with applying patchsets and new software releases.

逻辑备用可以升级到新版本，然后切换为活动主版本。

A logical standby can be upgraded to the new release and then switched over to become the active primary.

这允许在旧的主设备转换为逻辑备用设备并应用补丁集时实现完全可用性。

This allows full availability while the old primary is converted to a logical standby and the patchset is applied.

逻辑备用程序为DBMS\u ROLLING PL/SQL包提供了底层平台，它提供的功能允许您在滚动升级和其他存储重组的上下文中使您的Oracle Data Guard配置高度可用。

Logical standbys provide the underlying platform for the DBMS_ROLLING PL/SQL package, which provides functionality that allows you to make your Oracle Data Guard configuration highly available in the context of rolling upgrades and other storage reorganization.

最大限度地减少软件升级的停机时间

• Support for reporting and decision support requirements
逻辑备用的一个关键好处是可以创建重要的辅助结构来优化报告工作量；
A key benefit of logical standby is that significant auxiliary structures can be created to optimize the reporting workload; 
可能对主服务器的事务响应时间产生禁止性影响的结构。
structures that could have a prohibitive impact on the primary's transactional response time. 
逻辑备用可以将其数据物理地重新组织为具有不同分区的不同存储类型，具有许多不同的索引，创建和维护按需刷新物化视图，并且可以用于驱动数据多维数据集和其他OLAP数据视图的创建。
A logical standby can have its data physically reorganized into a different storage type with different partitioning, have many different indexes, have on-demand refresh materialized views created and maintained, and can be used to drive the creation of data cubes and other OLAP data views.
但是，逻辑备用数据库不允许对数据进行任何转换（例如仅复制列的子集或允许在用户表上添加列）。
However, a logical standby database does not allow for any transformation of your data (such as replicating only a subset of columns or allowing additional columns on user tables). 
对于这些类型的报告活动，Oracle GoldenGate是Oracle的首选解决方案。
For those types of reporting activities, Oracle GoldenGate is Oracle's preferred solution.

• Support for reporting and decision support requirements

逻辑备用的一个关键好处是可以创建重要的辅助结构来优化报告工作量；

A key benefit of logical standby is that significant auxiliary structures can be created to optimize the reporting workload;

可能对主服务器的事务响应时间产生禁止性影响的结构。

structures that could have a prohibitive impact on the primary's transactional response time.

逻辑备用可以将其数据物理地重新组织为具有不同分区的不同存储类型，具有许多不同的索引，创建和维护按需刷新物化视图，并且可以用于驱动数据多维数据集和其他OLAP数据视图的创建。

A logical standby can have its data physically reorganized into a different storage type with different partitioning, have many different indexes, have on-demand refresh materialized views created and maintained, and can be used to drive the creation of data cubes and other OLAP data views.

但是，逻辑备用数据库不允许对数据进行任何转换（例如仅复制列的子集或允许在用户表上添加列）。

However, a logical standby database does not allow for any transformation of your data (such as replicating only a subset of columns or allowing additional columns on user tables).

对于这些类型的报告活动，Oracle GoldenGate是Oracle的首选解决方案。

For those types of reporting activities, Oracle GoldenGate is Oracle's preferred solution.

2.3 Snapshot Standby Databases

快照备用数据库是一种可更新的备用数据库，为主数据库提供完整的数据保护。
A snapshot standby database is a type of updatable standby database that provides full data protection for a primary database.
快照备用数据库从其主数据库接收并存档（但不应用）重做数据。
A snapshot standby database receives and archives, but does not apply, redo data from its primary database. 
在放弃对快照备用数据库的所有本地更新后，当快照备用数据库转换回物理备用数据库时，将应用从主数据库接收的重做数据。
Redo data received from the primary database is applied when a snapshot standby database is converted back into a physical standby database, after discarding all local updates to the snapshot standby database.
快照备用数据库随着时间的推移会与其主数据库分离，因为主数据库中的重做数据在接收时不会应用。
A snapshot standby database diverges from its primary database over time because redo data from the primary database is not applied as it is received. 
对快照备用数据库的本地更新会导致其他分歧。
Local updates to the snapshot standby database cause additional divergence. 
但是，主数据库中的数据是完全受保护的，因为可以随时将快照备用数据库转换回物理备用数据库，然后应用从主数据库接收的重做数据。
The data in the primary database is fully protected however, because a snapshot standby can be converted back into a physical standby database at any time, and the redo data received from the primary is then applied.

快照备用数据库是一种可更新的备用数据库，为主数据库提供完整的数据保护。

A snapshot standby database is a type of updatable standby database that provides full data protection for a primary database.

快照备用数据库从其主数据库接收并存档（但不应用）重做数据。

A snapshot standby database receives and archives, but does not apply, redo data from its primary database.

在放弃对快照备用数据库的所有本地更新后，当快照备用数据库转换回物理备用数据库时，将应用从主数据库接收的重做数据。

Redo data received from the primary database is applied when a snapshot standby database is converted back into a physical standby database, after discarding all local updates to the snapshot standby database.

快照备用数据库随着时间的推移会与其主数据库分离，因为主数据库中的重做数据在接收时不会应用。

A snapshot standby database diverges from its primary database over time because redo data from the primary database is not applied as it is received.

对快照备用数据库的本地更新会导致其他分歧。

Local updates to the snapshot standby database cause additional divergence.

但是，主数据库中的数据是完全受保护的，因为可以随时将快照备用数据库转换回物理备用数据库，然后应用从主数据库接收的重做数据。

The data in the primary database is fully protected however, because a snapshot standby can be converted back into a physical standby database at any time, and the redo data received from the primary is then applied.

快照备用数据库的好处

Benefits of a Snapshot Standby Database
快照备用数据库是完全可更新的备用数据库，它提供了与物理备用数据库类似的灾难恢复和数据保护好处。
A snapshot standby database is a fully updatable standby database that provides disaster recovery and data protection benefits that are similar to those of a physical standby database. 
快照备用数据库最好用在这样的场景中：主数据库有一个临时的、可更新的快照，这样可以增加从主数据库故障中恢复的时间。
Snapshot standby databases are best used in scenarios where the benefit of having a temporary, updatable snapshot of the primary database justifies the increased time to recover from primary database failures.

Benefits of a Snapshot Standby Database

快照备用数据库是完全可更新的备用数据库，它提供了与物理备用数据库类似的灾难恢复和数据保护好处。

A snapshot standby database is a fully updatable standby database that provides disaster recovery and data protection benefits that are similar to those of a physical standby database.

快照备用数据库最好用在这样的场景中：主数据库有一个临时的、可更新的快照，这样可以增加从主数据库故障中恢复的时间。

Snapshot standby databases are best used in scenarios where the benefit of having a temporary, updatable snapshot of the primary database justifies the increased time to recover from primary database failures.

使用快照备用数据库的好处包括：

The benefits of using a snapshot standby database include the following:
•它为开发和测试的提供生产数据库的精确副本，同时始终保持数据保护。
• It provides an exact replica of a production database for development and testing purposes, while maintaining data protection at all times. 
您可以使用Oracle Real Application Testing选项捕获主数据库工作负载，然后在snapshot备用服务器上重放它以进行测试。
You can use the Oracle Real Application Testing option to capture primary database workload and then replay it for test purposes on the snapshot standby.
•通过转换为物理备用并重新同步，可以轻松刷新以包含当前生产数据。
• It can be easily refreshed to contain current production data by converting to a physical standby and resynchronizing.
创建快照备用、测试、与生产重新同步，然后再次创建快照备用和测试的能力是一个可以根据需要重复的周期。
The ability to create a snapshot standby, test, resynchronize with production, and then again create a snapshot standby and test, is a cycle that can be repeated as often as desired. 
在需要对数据进行读/写访问的情况下，可以使用相同的过程轻松创建和定期更新备用快照，以便进行报告。
The same process can be used to easily create and regularly update a snapshot standby for reporting purposes where read/write access to data is required.

The benefits of using a snapshot standby database include the following:

•它为开发和测试的提供生产数据库的精确副本，同时始终保持数据保护。

• It provides an exact replica of a production database for development and testing purposes, while maintaining data protection at all times.

您可以使用Oracle Real Application Testing选项捕获主数据库工作负载，然后在snapshot备用服务器上重放它以进行测试。

You can use the Oracle Real Application Testing option to capture primary database workload and then replay it for test purposes on the snapshot standby.

•通过转换为物理备用并重新同步，可以轻松刷新以包含当前生产数据。

• It can be easily refreshed to contain current production data by converting to a physical standby and resynchronizing.

创建快照备用、测试、与生产重新同步，然后再次创建快照备用和测试的能力是一个可以根据需要重复的周期。

The ability to create a snapshot standby, test, resynchronize with production, and then again create a snapshot standby and test, is a cycle that can be repeated as often as desired.

在需要对数据进行读/写访问的情况下，可以使用相同的过程轻松创建和定期更新备用快照，以便进行报告。

The same process can be used to easily create and regularly update a snapshot standby for reporting purposes where read/write access to data is required.

三：请描述如何将物理备用数据库转换为快照备用数据库;

Converting a Physical Standby Database into a Snapshot Standby Database
These steps describe how to convert a physical standby database into a snapshot standby database.
1. Stop Redo Apply, if it is active.
2. Ensure that the database is mounted, but not open.
3. Ensure that a fast recovery area has been configured. It is not necessary for flashback database to be enabled.
4. Issue the following SQL statement to perform the conversion:
SQL> ALTER DATABASE CONVERT TO SNAPSHOT STANDBY;
5. Open the snapshot standby in read/write mode by issuing the following SQL statement:
SQL> ALTER DATABASE OPEN READ WRITE;

Converting a Physical Standby Database into a Snapshot Standby Database

These steps describe how to convert a physical standby database into a snapshot standby database.

1. Stop Redo Apply, if it is active.

2. Ensure that the database is mounted, but not open.

3. Ensure that a fast recovery area has been configured. It is not necessary for flashback database to be enabled.

4. Issue the following SQL statement to perform the conversion:

SQL> ALTER DATABASE CONVERT TO SNAPSHOT STANDBY;

5. Open the snapshot standby in read/write mode by issuing the following SQL statement:

SQL> ALTER DATABASE OPEN READ WRITE;

四：请描述如何将快照备用数据库转换为物理备用数据库;

Converting a Snapshot Standby Database into a Physical Standby Database
These steps describe how to convert a snapshot standby database into a physical standby database.
1. On an Oracle Real Applications Cluster (Oracle RAC) database, shut down all but one instance.
2. Ensure that the database is mounted, but not open.
3. Issue the following SQL statement to perform the conversion:
SQL> ALTER DATABASE CONVERT TO PHYSICAL STANDBY;
Redo data received while the database was a snapshot standby database is automatically applied

Converting a Snapshot Standby Database into a Physical Standby Database

These steps describe how to convert a snapshot standby database into a physical standby database.

1. On an Oracle Real Applications Cluster (Oracle RAC) database, shut down all but one instance.

2. Ensure that the database is mounted, but not open.

3. Issue the following SQL statement to perform the conversion:

SQL> ALTER DATABASE CONVERT TO PHYSICAL STANDBY;

Redo data received while the database was a snapshot standby database is automatically applied

五：请描述DG环境需要配置哪些参数;

设置主数据库初始化参数
Set Primary Database Initialization Parameters

1 2	设置主数据库初始化参数 Set Primary Database Initialization Parameters

1.DB_NAME

示例：
DB_NAME=chicago
说明：
在主数据库上，指定创建数据库时使用的名称。
On a primary database, specify the name used when the database was created.
在物理备用数据库上，使用主数据库的DB_NAME名称。
On a physical standby database, use the DB_NAME of the primary database.

示例：

DB_NAME=chicago

说明：

在主数据库上，指定创建数据库时使用的名称。

On a primary database, specify the name used when the database was created.

在物理备用数据库上，使用主数据库的DB_NAME名称。

On a physical standby database, use the DB_NAME of the primary database.

2.DB_UNIQUE_NAME

示例：
DB_UNIQUE_NAME=chicago
说明：
为每个数据库指定唯一的名称。
Specify a unique name for each database. 
此名称将保留在数据库中，并且不会更改，即使主数据库和备用数据库反转角色也是如此。
This name stays with the database and does not change, even if the primary and standby databases reverse roles.

示例：

DB_UNIQUE_NAME=chicago

说明：

为每个数据库指定唯一的名称。

Specify a unique name for each database.

此名称将保留在数据库中，并且不会更改，即使主数据库和备用数据库反转角色也是如此。

This name stays with the database and does not change, even if the primary and standby databases reverse roles.

3.LOG_ARCHIVE_CONFIG

示例：
LOG_ARCHIVE_CONFIG='DG_CONFIG=(chicago,boston)'
说明：
必须在Oracle Data Guard配置中的每个数据库上显式设置此参数的DG_CONFIG属性，以启用完整的Oracle Data Guard功能。
The DG_CONFIG attribute of this parameter must be explicitly set on each database in an Oracle Data Guard configuration to enable full Oracle Data Guard functionality. 
将DG_CONFIG设置为包含配置中每个数据库的DB_UNIQUE_NAME的文本字符串，该列表中的每个名称用逗号分隔。
Set DG_CONFIG to a text string that contains the DB_UNIQUE_NAME of each database in the configuration, with each name in this list separated by a comma.

示例：

LOG_ARCHIVE_CONFIG='DG_CONFIG=(chicago,boston)'

说明：

必须在Oracle Data Guard配置中的每个数据库上显式设置此参数的DG_CONFIG属性，以启用完整的Oracle Data Guard功能。

The DG_CONFIG attribute of this parameter must be explicitly set on each database in an Oracle Data Guard configuration to enable full Oracle Data Guard functionality.

将DG_CONFIG设置为包含配置中每个数据库的DB_UNIQUE_NAME的文本字符串，该列表中的每个名称用逗号分隔。

Set DG_CONFIG to a text string that contains the DB_UNIQUE_NAME of each database in the configuration, with each name in this list separated by a comma.

4.CONTROL_FILES

示例：
CONTROL_FILES='/arch1/chicago/control1.ctl', '/arch2/chicago/control2.ctl'
说明：
指定主数据库上控制文件的路径名。
Specify the path name for the control files on the primary database. 
建议提供控制文件的第二个副本，以便在将好的控制文件复制到坏的控制文件位置后，可以轻松地重新启动实例。
It is recommended that a second copy of the control file is available so an instance can be easily restarted after copying the good control file to the location of the bad control file.

示例：

CONTROL_FILES='/arch1/chicago/control1.ctl', '/arch2/chicago/control2.ctl'

说明：

指定主数据库上控制文件的路径名。

Specify the path name for the control files on the primary database.

建议提供控制文件的第二个副本，以便在将好的控制文件复制到坏的控制文件位置后，可以轻松地重新启动实例。

It is recommended that a second copy of the control file is available so an instance can be easily restarted after copying the good control file to the location of the bad control file.

5.LOG_ARCHIVE_DEST_1

本人提供Oracle(OCP、OCM)、MySQL(OCP)、PostgreSQL(PGCA、PGCE、PGCM)等数据库的培训和考证业务，私聊QQ646634621或微信dbaup66，谢谢！

后续精彩内容已被站长无情隐藏，请输入验证码解锁本文！

获取验证码：请先关注本站微信公众号，然后回复“验证码”，获取验证码。在微信里搜索“AiDBA”或者“dbaup6”或者微信扫描右侧二维码都可以关注本站微信公众号。

打赏赞(1)

标签： Oracle 高可用面试笔试 DG

小麦苗

学习或考证，均可联系麦老师，请加微信db_bao或QQ646634621

发表回复取消回复

要发表评论，您必须先登录。

一	二	三	四	五	六	日
	1	2	3	4	5	6
7	8	9	10	11	12	13
14	15	16	17	18	19	20
21	22	23	24	25	26	27
28	29	30	31

合 Oracle DBA面试笔试之高可用DG灾备系列

在Oracle中，什么是DG？DG有哪些优缺点？

在Oracle中，请简单描述DG的架构。

在Oracle中，有哪几种类型的DG？

在Oracle中，搭建物理DG需要注意的地方有哪些？

在Oracle中，将一个物理DG转换为逻辑DG有哪些步骤呢？

在Oracle中，物理DG和快照DG相互转换的步骤有哪些？

在Oracle的DG中，RFS、LNSn、MRP、LSP进程的作用分别是什么？

在Oracle的DG中，有哪些重要的参数，它们分别代表什么含义？

在Oracle中，DG有哪3种保护模式？

在Oracle的DG中，Switchover和Failover的区别有哪些？

在Oracle中，如果主库丢失归档文件，那么物理DG如何恢复？

在Oracle中，备库数据文件异常，物理DG如何恢复？

在Oracle中，DG中GAP有几种解决方案？

在Oracle中，DG中常常用到的比较有用的性能视图有哪些？

在Oracle中，物理DG维护中常用到的SQL语句有哪些？

在Oracle中，逻辑DG维护中常用到的SQL语句有哪些？

在Oracle中，RAC、DG和OGG的区别有哪些？

其它DG基础知识

一：请描述Oracle Data Guard优点有哪些

二：请描述DG备库类型和特点

三：请描述如何将物理备用数据库转换为快照备用数据库;

四：请描述如何将快照备用数据库转换为物理备用数据库;

五：请描述DG环境需要配置哪些参数;

相关文章

您可能还喜欢...

发表回复取消回复

网站公告

网站寄语

本站其它工具

搜索本网站

标签云☁

网站日历

网站归档

网站分类

合 Oracle DBA面试笔试之高可用DG灾备系列

在Oracle中，什么是DG？DG有哪些优缺点？

在Oracle中，请简单描述DG的架构。

在Oracle中，有哪几种类型的DG？

在Oracle中，搭建物理DG需要注意的地方有哪些？

在Oracle中，将一个物理DG转换为逻辑DG有哪些步骤呢？

在Oracle中，物理DG和快照DG相互转换的步骤有哪些？

在Oracle的DG中，RFS、LNSn、MRP、LSP进程的作用分别是什么？

在Oracle的DG中，有哪些重要的参数，它们分别代表什么含义？

在Oracle中，DG有哪3种保护模式？

在Oracle的DG中，Switchover和Failover的区别有哪些？

在Oracle中，如果主库丢失归档文件，那么物理DG如何恢复？

在Oracle中，备库数据文件异常，物理DG如何恢复？

在Oracle中，DG中GAP有几种解决方案？

在Oracle中，DG中常常用到的比较有用的性能视图有哪些？

在Oracle中，物理DG维护中常用到的SQL语句有哪些？

在Oracle中，逻辑DG维护中常用到的SQL语句有哪些？

在Oracle中，RAC、DG和OGG的区别有哪些？

其它DG基础知识

一：请描述Oracle Data Guard优点有哪些

二：请描述DG备库类型和特点

三：请描述如何将物理备用数据库转换为快照备用数据库;

四：请描述如何将快照备用数据库转换为物理备用数据库;

五：请描述DG环境需要配置哪些参数;

相关文章

您可能还喜欢...

在非域环境下搭建MSSQL 2016高可用之镜像传输

Oracle重命名表空间

使用数据泵+OGG微服务新参数ENABLE_INSTANTIATION_FILTERING零停机迁移12c到19c

发表回复 取消回复

网站公告

网站寄语

本站其它工具

搜索本网站

标签云☁

网站日历

网站归档

网站分类

发表回复取消回复