Go to main content

Oracle® Solaris Cluster Geographic Edition Data Replication Guide for Oracle Data Guard

Exit Print View

Updated: June 2017
 
 
Chapter 1

Replicating Data With Oracle Data Guard Software

This chapter describes how to configure data replication with Oracle Data Guard software in an Oracle Solaris Cluster Geographic Edition (Geographic Edition) environment.

This chapter covers the following topics:

Geographic Edition software supports the use of Oracle Data Guard for data replication when used with HA for Oracle Database, HA for Oracle External Proxy, or Oracle RAC software.

Beginning with Oracle Solaris Cluster 4.2 SRU 1, Geographic Edition software also supports the use of Oracle Data Guard instances running on a system that is not under Oracle Solaris Cluster control, called a remote node. Replication can be performed between two databases that are both running on remote nodes, or performed between a database on a remote node and another database on a cluster node that is configured with Geographic Edition software.


Note -  To manage an Oracle Data Guard database on a remote node, you must configure the HA for Oracle External Proxy resource for the remote database instance on the same cluster where you create the protection group.

Before you can replicate data with Oracle Data Guard, you must be familiar with the Oracle Data Guard documentation. For information about installing and configuring the Oracle Data Guard software and its latest patches, see the Oracle Data Guard documentation. If you plan to configure an Oracle Data Guard database on a remote node, also see Oracle Solaris Cluster Data Service for Oracle External Proxy Guide.

During data replication, data from a primary cluster is copied to a backup, or standby cluster. The standby cluster can be located at a site that is geographically separated from the primary cluster. The distance between the primary and standby clusters depends on the distance that your data replication product supports.


Caution

Caution  -  When using HA for Oracle Database for an Oracle Data Guard database instance, take special care to coordinate the switchover with HA for Oracle Database. HA for Oracle Database monitors the database and will take action when the database's state changes unexpectedly. Likewise, when Geographic Edition is used to remotely manage an Oracle Data Guard database instance, the remote node must not have HA for Oracle Database configured for this Oracle Data Guard instance. When both HA for Oracle Database and Geographic Edition are used for the same Oracle Data Guard database instance on the same Oracle Solaris Cluster node, if you must switch over the Oracle Data Guard state directly, first unmonitor the HA for Oracle Database resource. After the switchover is done, ensure that the Dataguard_role and Standby_mode resource properties exactly match the current database settings locally, before you re-enable monitoring of the HA for Oracle Database resource. Failure to take these precautions might result in HA for Oracle Database issuing database restarts and failing to stay online.


The example procedures in this chapter show how to configure Oracle Data Guard to replicate data between a primary and a standby database.