In sweet memories of my ever loving brother "kutty thambi " ARUN KUMAR

Monday, January 25, 2010

fast-start failover DATAGUARD BROKER

here is an example to check the fast start failover in dataguard environment
i manually killed the mandatory background process smon of primary database.
then the observer automatically initiate the standby database to primary database, and reinstate the old primary database to standby.


here, primary database name: whiteowl
physical standby database name: blackowl

observer name: observer

from primary database machine rac1:
[oracle@rac1 ~]$ ps -eaf | grep smon
oracle   17328     1  0 12:25 ?        00:00:00 ora_smon_whiteowl
oracle   17886 17865  0 12:34 pts/4    00:00:00 grep smon
[oracle@rac1 ~]$ kill -9 17428

startup the primary database in mount stage.

DGMGRL> show configuration verbose;

Configuration
  Name:                whiteowl
  Enabled:             YES
  Protection Mode:     MaxAvailability
  Fast-Start Failover: ENABLED
  Databases:
    whiteowl - Physical standby database (disabled)
             - Fast-Start Failover target
    blackowl - Primary database

Fast-Start Failover
  Threshold: 30 seconds
  Observer:  rac1

Current status for "whiteowl":
Warning: ORA-16608: one or more databases have warnings


DGMGRL> show site verbose 'blackowl';
Site
  Name:                          'blackowl'
  Hostname:                      'rac2'
  Instance name:                 'blackowl'
  Service Name:                  'blackowl'
  Standby Type:                  'physical'
  Enabled:                       'yes'
  Required:                      'yes'
  Default state:                 'PRIMARY'
  Intended state:                'PRIMARY'
  PFILE:                         ''
  Number of resources:  1
  Resources:
    Name: blackowl (default) (verbose name='blackowl')
Current status for "blackowl":
Warning: ORA-16817: unsynchronized Fast-Start Failover configuration

DGMGRL> show site verbose 'whiteowl';
Site
  Name:                          'whiteowl'
  Hostname:                      'rac1'
  Instance name:                 'whiteowl'
  Service Name:                  'whiteowl'
  Standby Type:                  'physical'
  Enabled:                       'yes'
  Required:                      'yes'
  Default state:                 'STANDBY'
  Intended state:                'STANDBY'
  PFILE:                         ''
  Number of resources:  1
  Resources:
    Name: whiteowl (default) (verbose name='whiteowl')
Current status for "whiteowl":
Warning: ORA-16817: unsynchronized Fast-Start Failover configuration


on observer: machine rac3

12:19:20.23  Monday, January 25, 2010
Initiating fast-start failover to database "blackowl"...
Performing failover NOW, please wait...
Failover succeeded, new primary is "blackowl"
12:19:51.84  Monday, January 25, 2010

12:24:33.93  Monday, January 25, 2010
Initiating reinstatement for database "whiteowl"...
Reinstating database "whiteowl", please wait...
Operation requires shutdown of instance "whiteowl" on database "whiteowl"
Shutting down instance "whiteowl"...
ORA-01109: database not open

Database dismounted.
ORACLE instance shut down.
Operation requires startup of instance "whiteowl" on database "whiteowl"
Starting instance "whiteowl"...
ORACLE instance started.
Database mounted.
Continuing to reinstate database "whiteowl" ...
Reinstatement of database "whiteowl" succeeded
12:26:02.89  Monday, January 25, 2010

then check,
DGMGRL> show configuration verbose;

Configuration
  Name:                whiteowl
  Enabled:             YES
  Protection Mode:     MaxAvailability
  Fast-Start Failover: ENABLED
  Databases:
    whiteowl - Physical standby database
             - Fast-Start Failover target
    blackowl - Primary database

Fast-Start Failover
  Threshold: 30 seconds
  Observer:  rac1

Current status for "whiteowl":
SUCCESS

regards,
rajeshkumar

No comments:

 
Share/Bookmark