Go to main content

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

Exit Print View

Updated: June 2017
 
 

Synchronizing Roles Between an Oracle Data Guard Configuration and its Geographic Edition Protection Group

Under certain circumstances after a switchover, the protection group roles might no longer match the database roles. Examples of when this might happen are if the Database Administrator issues an Oracle Data Guard switchover directly, or if checks run during a protection-group switchover fail but the switchover successfully completes. If the protection group and database roles no longer match, you must manually synchronize them.

How to Synchronize the Roles of an Oracle Data Guard Configuration and its Geographic Edition Protection Group

Perform this procedure to change the roles of a Geographic Edition protection group to match the roles of an Oracle Data Guard configuration that has been switched.

  1. Assume the root role on the Oracle Data Guard primary where the Oracle Data Guard protection group has a secondary role.
  2. Compare the database and protection-group roles to confirm that they do not match.
    # clresource status odg-configuration-odg-rep-rs
    1. The siamst_siamstdr-odg-rep-rs shows:
      Faulted - Role "physical standby database" given for database local-database does not 
      match role "primary database" configured Oracle Data Guard.
    2. Display the protection group status.
      # geadm status
         Cluster: cluster-paris
      
         Partnership "paris-newyork-ps"      : OK
             Partner clusters        : cluster-newyork
             Synchronization         : OK
             ICRM Connection         : OK
      
             Heartbeat "hb_cluster-paris~cluster-newyork" monitoring "cluster-newyork": OK
                  Plug-in "ping_plugin"      : Inactive
                  Plug-in "tcp_udp_plugin"   : OK
      
         Protection group "odg-pg"    : Error
              Partnership             : paris-newyork-ps
              Synchronization         : OK
      
              Cluster cluster-paris           : Error
                   Role               : Secondary
                   Activation state   : Activated
                   Configuration      : Error
                   Data replication   : Error
                   Resource groups    : OK
      
              Cluster cluster-newyork         : Error
                   Role               : Primary
                   Activation state   : Deactivated
                   Configuration      : Error
                   Data replication   : Error
                   Resource groups    : OK
    3. Display the database configuration.
      DGMGRL> show configuration;
      Configuration
        Name:               odg-configuration
        Enabled:            YES
        Protection Mode:    MaxPerformance
        Databases:
          local-database   - Primary database
          remote-database - Physical standby database
      
      Fast-Start Failover: DISABLED
      
      Current status for "odg-configuration":
      SUCCESS
      
      DGMGRL>
  3. From one node of the protection group's secondary cluster, deactivate the protection group locally.
    phys-paris-1# geopg stop -e local odg-pg
  4. From one node of the protection group's secondary cluster, issue a takeover.
    phys-paris-1# geopg takeover -f odg-pg
    Processing operation... The timeout period for this operation on each cluster 
    is 3600 seconds (3600000 milliseconds)…
    "Takeover" operation succeeded for the protection group "odg-pg".
    phys-paris-1#
  5. From one node of the protection group's primary and secondary cluster, validate the protection group.
    phys-paris-1# geopg validate odg-pg
    phys-newyork-1# geopg validate odg-pg
  6. From one node of either cluster start pg globally.
    phys-paris-1# geopg start -e global odg-pg
    Processing operation... The timeout period for this operation on each cluster
    is 3600 seconds (3600000 milliseconds)…
    Protection group "odg-pg" successfully started.
    phys-paris-1#
  7. Verify the protection group status.
    phys-paris-1# geoadm status
       Cluster: cluster-paris
    
       Partnership "paris-newyork-ps"      : OK
           Partner clusters        : cluster-newyork
           Synchronization         : OK
           ICRM Connection         : OK
    
           Heartbeat "hb_cluster-paris~cluster-newyork" monitoring "cluster-newyork": OK
                Plug-in "ping_plugin"      : Inactive
                Plug-in "tcp_udp_plugin"   : OK
    
       Protection group "odg-pg"    : OK
            Partnership             : paris-newyork-ps
            Synchronization         : OK
    
            Cluster cluster-paris           : OK
                 Role               : Primary
                 Activation state   : Activated
                 Configuration      : OK
                 Data replication   : OK
                 Resource groups    : OK
    
            Cluster cluster-newyork         : OK
                 Role               : Secondary
                 Activation state   : Activated
                 Configuration      : OK
                 Data replication   : OK
                 Resource groups    : OK