Automatic Failover

Data Guard has mpemented somethng caed Fast-start Failover (FSFO) whch uses
the Broker to perform the faover actons when there s a probem. Ths archtecture
uses a thrd member quorum that ensures that the faover occurs ony when
everythng meets the rues that you have dened, when the faover has happened
the prmary w never be aowed to open to avod any spt-bran scenaros, ths
woud be a bt of a nghtmare shoud both databases be open and processng
transactons.
The thrd member s caed the Observer and ts |ob s to mantan a connecton wth
the prmary and target standby databases, montorng there heath and performng
any faover's necessary, the Observer w aso renstate the od prmary when t
comes back on, f t can. The observer pngs the prmary database and that the rst
sgn of troube t w start to countdown (whch you congure), f t does re-estabsh
the connecton t w make a the necessary checks before goes back to watch mode
agan, f the tmer expres then t checks that the standby can take over and ntates
a faover, ths swtchover w have a automatcay and n the background usng the
Broker. If and when the prmary comes back the Observer w renstate the od
prmary as a standby database agan usng the Broker to acheve ths.
It s mport on where he Observer s paced n the network, ony one observer per
Data Guard nstaaton can be nstaed, so ths server must have access to both the
prmary and standby databases wth as much redundant networkng as possbe. Next
your thng s how much s the observer gong to cost me, not much as t can run on
most patforms and ony requred the Orace Cent Kt for the verson of Orace that
you are runnng, you must setup the TNSNAMES on the observer to aow t to png
the databases. If the Observer was to crash t w have no mpact on the current
Orace envronment, the ony mpact s that FSFO w not be avaabe unt the
Observer s up and runnng agan. The Observer can montorng the foowng
Database crash
System crash
The oss of the network
Compete ste outage
You can aso get FSFO to perform a shutdown abort on the prmary when other ssues
arse such as
Datae Omne
Corrupted Controe
Corrupted Dctonary
Inaccessbe Loge
Stuck Archver
The tags above must be entered as they are above otherwse the Broker w not
understand them
Montor a specc
condton va the
Broker
DGMGRL> enabe fast_start faover condton "Corrupted Controe";
DGMGRL> enabe fast_start faover condton "Datae Omne";
To dspay what you are montorng use
Dspay condtons
that are be montored
DGMGRL> show fast_start faover;
Fast-Start Faover: DISABLED
Threshod: 30 seconds
Target: (none)
Observer: (none)
Lag Lmt: 30 seconds
Shutdown Prmary: TRUE
Auto-renstate: TRUE
Congurabe Faover Condtons
Heath Condtons:
Corrupted Controe YES
Corrupted Dctonary YES
Inaccessbe Loge NO
Stuck Archver NO
Datae Omne YES
Orace Error Condtons:
(none)
Now that you have an overvew of FSFO t's tme to set t up and test t, |ust a quck
check before we progress, make sure that the foowng has been setup or congured
Use the Broker wth a ts prerequstes
Enabe ashback database on both prmary and standby
Setup the conguraton correcty for the protecton mode (standby redo ogs
es on both sdes, redo transport setup the same n both drectons)
Insta the Observer system and congure TNSNAME
If you are usng more than one standby you must et the Broker know whch one you
want to become the prmary, f you ony have one then the broker w know aready
Seect the standby to
become the prmary
DGMGRL> edt database prod1 set property FastStartFaoverTarget =
'prod1dr';
DGMGRL> edt database prod1dr set property FastStartFaoverTarget =
'prod1';
Now ts tme to dscuss how ong you shoud wat before you want to faover, you
don't want t too short |ust n case you network bps, by defaut t s set to 30
seconds but you can go down to 6 seconds f you wsh.
change threshod
DGMGRL> edt conguraton set property FastStartFaoverTargetThreshod =
45;
You can contro the amount of data oss, f usng one of the esser protecton modes,
the greater the ag mt set the greater the data oss, agan the tme s n seconds.
ag mt DGMGRL> edt conguraton set property FastStartFaoverLagLmt = 60;
If the data oss s ess then the mt the faover w proceed, f more redo woud be
oss than the ag mt, the faover w not occur and nothng happens unt the
prmary database ether comes back and processng contnues or you choose to
faover manuay, suherng the addtona data oss. If you are usng maxmum
protecton mode then ths property s gnored.
Here are two more addtona propertes that you can setup regardng the prmary,
one s to shutdown t down f t becomes hung and the other s to renstate t f a
faover does occur
abort prmary f n a hung
state
DGMGRL>edt conguraton set property
FastStartFaoverPmyShutdown = true;
renstate prmary after a
faover
DGMGRL>edt conguraton set property
FastStartFaoverAutoRenstate = true;
Once you are happy wth everythng you can now enabe the FSFO
Enabe FSFO
DGMGRL> enabe fast_start faover;
## Dspay the conguraton
DGMGRL> show fast_start faover;