Skip to main content

DATAGUARD

 VVV IMP TOPIC


The database should be in sync always


LSS - log shipment service

LNS - log network service

RFS - remote fetching service

MRP - managed recovery process

ARCH - archive process


Production Stand by

      DC DR


  LNS >>>>>>>>LSS>>>>>>>>>>RFS


Redolog files Rfs 

    Archives redolog files

      Lns online archives

                                                    Mrp

                                              Storage point


To see listner working or not fire command - ps – ef|grep tns


Alter database activate standby database; (to activate stand by at the time of server down)


Recover managed standby database disconnect from session > to on mrp


Alter database recover managed standby cancle > to off mrp



The archives in production data will send from LNS to RFS through LSS

LNS is in production RFS is in standby



          Production

        192.168.211.150


In primary database archive log should be enable


Archive log list

Enable

Disable

Shut immediately

Startup mount;

Alter database archive loglist

Alter database open

Select open_mode from v$ data base

Output readwrite

Force logging should be enable

Select force_logging from v$database;

Out put No 

Alter database force_logging

Output yes

Primary permissions

Standby permissions



Prime = prod

Address = protocal

Protocal = tcp

Host = ip address.153

Port = 1539

Server = dedicated

Service name = prod


Stand = stand by

Address = protocal

Protocal = tcp

Host = ip address.154

Port = 1539

Server = dedicated

Servicename = stand


Listner entry

Listner = description_list

Address = protocal

Protocal = tcp

Host = ip address

Port = 1539

Server = dedicated

Service = listner


Show paramater log

Log_archive_dest_1

Log_archive_dest_2

Log_archive_dest_3

……………………………

……………………………

Log_archive_dest_32


P-file

Db name = prod

Db unique name = power


Alter system set log_archive_config =’d.g’ config (power.super)scope = spfile;


Alter system set log_archive_dest = db home location scope = sp file;


Alter system set log _archive_dest_2 = service = stand scope = spfile;

                    Standby

            192.168.211.151





Archive log list

Enable

Disable

Shut immediately

Startup mount;

Alter database archive loglist

Alter database open

Select open_mode from v$ data base

Output readwrite

Force logging should be enable

Select force_logging from v$database;

Out put No 

Alter database force_logging

Output yes

Primary permissions

Standby permissions



Prime = prod

Address = protocal

Protocal = tcp

Host = ip address.153

Port = 1539

Server = dedicated

Service name = prod


Stand = stand by

Address = protocal

Protocal = tcp

Host = ip address.154

Port = 1539

Server = dedicated

Servicename = stand


Listner entry

Listner = description_list

Address = protocal

Protocal = tcp

Host = ip address

Port = 1539

Server = dedicated

Service = listner


Show paramater log

Log_archive_dest_1

Log_archive_dest_2

Log_archive_dest_3

……………………………

……………………………

Log_archive_dest_32


P-file

Db name = standby

Db unique name = super


Alter system set log_archive_config =’d.g’ config (power.super)scope = spfile;


Alter system set log_archive_dest = db home location scope = sp file;


Alter system set log _archive_dest_2 = service = prod scope = spfile;




Comments

Post a Comment

Popular posts from this blog

Oracle database single instance architecture

Oracle database single instance architecture  Maine database runs on a single machine we referred to this architecture as the Oracle database single instance architecture this setup involves having one Oracle database instance running on the mission serving its clients   The term Oracle database instance simply refers to the combination of memory structure and database process that collectively represent the database service.  However this Architectire has a significant availability risk.  If anything goes wrong with the mission that database becomes UN available.
Post a Comment
Read more

Table spaces

 Tablespace consists of one or more data files.  A data file belongs to only one tablespace. Segments, Extents, and Blocks • Segments exist within a tablespace • Segments are made up of a collection of extents • An extents is a collection of logically contiguous data blocks - Cannot span multiple data files • Data blocks are mapped to disk blocks SYSTEM and SYSAUX Tablespaces • The SYSTEM and SYSAUX tablespaces are mandatory tablespaces. • They are created at the time of database creation. • They must be online. • The SYSTEM tablespace is used for core functionality (for example, data dictionary tables). • The auxiliary SYSAUX tablespace is used for additional database components.
Post a Comment
Read more