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

Exit Print View

Updated: September 2014, E39669-02
 
 

Forcing a Takeover on Systems That Use Oracle Data Guard

You perform a takeover when applications need to be brought online on the standby cluster, regardless of whether the data is completely consistent between the primary database and the standby database. In this section, it is assumed that the protection group has been started.

The following operations occur after you initiate a takeover:

  • If the former primary cluster, cluster-paris, can be reached and the protection group is not locked for notification handling or some other reason, the protection group is deactivated.

    For a reminder of which cluster is cluster-paris, see Example Geographic Edition Cluster Configuration in Oracle Solaris Cluster Geographic Edition System Administration Guide .

  • Databases replicated in the Oracle Data Guard Broker configurations, which are present in the protection group that is being taken over from the former primary cluster cluster-paris, are taken over by the new primary cluster cluster-newyork.


    Note -  This data might not be consistent with the original databases. Data replication from the new primary cluster, cluster-newyork, to the former primary cluster, cluster-paris, is stopped.
  • The protection group is activated without data replication enabled. The former primary databases in each of the Oracle Data Guard Broker configurations that are taken over are placed in a disabled, recovery required, state.

For details about the possible conditions of the primary and standby clusters before and after a takeover, see Appendix D, Takeover Postconditions, in Oracle Solaris Cluster Geographic Edition System Administration Guide .