Professional Documents
Culture Documents
txt
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Disaster Recovery:
1: Oracle Streams
2: Materialized Views
3: Data Guard
Data Guard:
Standby Database
8i [Dummy Standby]
9i [Physical Standby Database or Real Standby Database]
MAX PERFORMACE:
PRIMARY:
LGWR
RLF
ARCHn
ALF
LTS (LNS or RFS)
ALF
LAS (MRPn)
STANDBY MOUNT
(or)
MAX PROTECTION:
PRIMARY STANDBY MOUNT
LGWR 1 RLF
2
RLF ARCHn LAS or MRPn
ARCHn ALF
ALF
MAX AVAILABILITY:
PRIMARY STANDBY MOUNT
LGWR 1 RLF
2
RLF ARCHn
ARCHn ALF
ALF LAS (MRPn) => STANDBY MOUNT
If Failure
FAL SERVER/CLIENT
ALF
LTS
ALF => FAL SERVER/CLIENT =>STANDBY MOUNT
Real-Time Apply:
PRIMARY STANDBY MOUNT
LGWR => RLF => LAS (MRPn) => STANDBY MOUNT
RLF ARCHn
ARCHn ALF
ALF
In 10g, we can open the standby database in Read Only Mode, But there is some
restriction.
Log shipping will continue but log apply will not apply.
In 11g, If we open standby database in read only mode, then Log apply service & Log
shipping will both work.
#ifconfig
Query this command, if any thing wrong with the standby database:
SELECT max(sequence#) from v$log_history;
By querying this command, in both PDB & SDB, If the result is same, then OK, else
something is wrong.
Yes No
Check
1: MRP P rocess
2: Shutdown Standby Database & Startup
3: Check the alert log files for both Primary & Standby Database
In the Primary Database, FAL_CLIENT will be Primary Database name, & FAL_SERVER
name will give the standby database name.
In Standby database parameter file, FAL_CLIENT will be standby database name &
FAL_SERVER name will be primary database name.
FAL_SERVER & FAL_CLIENT will be used while archive gaps occur between Primary
database & Standby database.
FAL_CLIENT will intimate the archive number to FAL_SERVER of the primary database,
then the FAL_SERVER of the primary database will intimate the LTS (