You are on page 1of 3

g:\prints\dataguard1\datagurad.

txt
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Disaster Recovery:
1: Oracle Streams
2: Materialized Views
3: Data Guard

IBM Introduced Active/Passive Server


From this concept, Data Guard Occured.

Data Guard:
Standby Database
8i [Dummy Standby]
9i [Physical Standby Database or Real Standby Database]

1: MAX PERFORMANCE (LGWR ASYNC)


2: MAX PROTECTION (LGWR SYNC AFFIRM)
3: MAX AVAILABILITY (LGWR SYNC NOAFFIRM)

MAX PERFORMACE:

PRIMARY:
LGWR
RLF
ARCHn
ALF
LTS (LNS or RFS)
ALF
LAS (MRPn)
STANDBY MOUNT

LTS: Log Transport Service


LNS: Log Network Service

(or)

RFS: Remote File Service


LAS: Log Apply Service
MRPn: Managed Recovery Process

MAX PROTECTION:
PRIMARY STANDBY MOUNT
LGWR 1 RLF
2
RLF ARCHn LAS or MRPn
ARCHn ALF
ALF

MAX AVAILABILITY = MAX PERFORMANCE + MAX PROTECTION

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

FAL: Fetch Archive Log.


FAL is a Background Process.

When the Archive Gap occur, who will recover?

FAL_SERVER & FAL_CLIENT

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.

Logical Standby Database:


PRIMARY STANDBY (READ-WRITE)
LGWR SQL APPLY
RLF SQL STATUS
ARCHn Log Miner
ALF => ALF

After configuring Standby Database, if we create a TS in Primary Database, Then How


this TS will be updated in Standby Database.

Difference Between Physical Standby Database & Logical Standby Database:


In Physical Standby Database, the database will be in Mount or Read-only Mode.

Here in Logical Standby Database, the database will be in Read/Write Mode.

Configuring Standby Database

OraInventory stores all the oracle Installed Files.


Means all the RDBMS files.
OraInventory is a Repository.

$tail -f alert log file

#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.

SELECT SEQUENCE#, ARCHIVED, APPLIED FROM V$ARCHIVED_LOG;

Yes No

Check
1: MRP P rocess
2: Shutdown Standby Database & Startup
3: Check the alert log files for both Primary & Standby Database

Swithover & Failover

Difference Between Physical Standby & Logical Standby:


Main Difference:
Physical Standby: We can not make the database to read-write
Logical Standby: We can make the database in read-write

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 (

You might also like