DATA GUARD

High availability
..
Data base
Control and redo log file can be get be protected by multiplexing
Data base file can be replicate to different location by data guard
DATA GUARD is applied across the sitesif primary DB down and so we can
access secondary DB
RACreal application cluster with in site to protect from the instance failure
10g and 11g difference operation mainly active stand by
STAND BY-11g
Primary DBNEWYORK
Secondary DBINDIA(physical stand by)
n/w set up b/whigh band width and low latency
Main component DG the N/w after set up
n/w transmit data from primary to secondary that depends on type of protection
modes
PROTECTION MODES
Max performanceREDOLOG FILES
Must and need standby for PROD to function
Max protectionwhen set up DG by default in max due to ARCHEIVE
log file
Max availabilityREDO LOG BOTH NEED STANDBY
If no standby available than also PROD can function
As on when archieve log file is generate in PROD is sifted to sec (stand
by)where sec is MRMmanage recovery mode.as a on when archieve log
is shifted from pm to sec is applied.
There may loss of data when redo log files lost on PROD .so to protect the
transaction file which are not made to available to ORACLE file so we can
implant to max protect up to last commit
If commit data will return to redo log once it done .if PROD go down still
transaction on stand bye so need to be stand redo loge by in sec
so stand by redo log shift protection mode max performance to max
protection.
PROD enable max protection all transaction commit to in PROD has to
return to standby redo log so get commit complete msg
..DURING max protection if standby goes down than primary cant
function.
## During max protection both standby and primary availability is must
So whatever information in redo log of primary must be in the standby of
redo log of secondary.

MAX AVAILABLE
Its like max protection in case no standby available then also PRIMARY
can function.

In 11g to read STANDBY we need to bring it out from MRM mode(no

longer in recovery) mean will standby of archecive log get generated and
we put back to MRM mode then all archeive log get applied in standby

11g2ACTIVE STANDBY even standby in MRM we can readonly the

data
So due to this advantage is DATAGUARD
Due to above advantage is primary is left as OLTP (online transaction processing)
and thereby standby as reporting stuff etc.

Status-
primary
SQL>select protection_mode,database_mode V$database;
SQL>alter system

Sandyby
SQL>alter database open read only;
SQL>alter database recovery managed standby database disconnect;MRM
mode
SQL>archive log listno mount state
 SQL>alter database managed standby database cancelpull out from recovery
mode
SQl>alter database recovery managed standby database disconnect using
current redo log file;
To change mode to other we need have stand by redo log.
To create stand by redo log group in stand by
Done after offing the recovery mode
SQL>alter database add standby logfile group <number><location> size <>m;

Change PROD to max availability (primary)

DATA BASE in mount state
SQL>alter database set standby database to maximize availability;
SQL>alter database open;
SQL>select protection_mode,database_mode V$database;