Karan Rajpoot Oracle DBA Blog's

In my previous blog, We saw the configuration steps of the data guard setup . In this blog, we will see the configuration of DGMGRL Oracle utility. let's start the configuration. Step 1) First we should check the DB name, DB unique name, open_mode, database_role of both the servers. Primary Server: - SQL>  select name, db_unique_name,open_mode,database_role, flashback_on from v$database; NAME   DB_UNIQUE_NAME OPEN_MODE       DATABASE_ROLE    FLASHBACK_ON --------- ------------------------------ -------------------- ---------------- ------------------ PROD   prod READ WRITE       PRIMARY        YES Standby Server: - SQL> select name, db_unique_name,open_mode,database_role, flashback_on from v$database; NAME   DB_UNIQUE_NAME OPEN_MODE       DATABASE_ROLE    FLASHBACK_ON --------- ------------------------------ -------------------- ---------------- ------------------ PROD   dr MOUNTED       PHYSICAL STANDBY YES Step 2) Now test th

Required Parameters to configure the Dataguard setup:- DB_NAME= It should be the same on the primary and standby side. DB_UNIQUE_NAME= Must be different on the primary and dr side. LOG_ARCHIVE_CONFIG= This parameter includes db_unique_name which is the part of data guard configuration. LOG_ARCHIVE_DEST_n=   It defines the local and remote archive log file location. LOG_ARCHIVE_DEST_STATE_n=  It defines the state of archiving (enable or differ). REMOTE_LOGIN_PASSWORDFILE=  it should be in EXCLUSIVE mode. FAL_SERVER= Use for archive log gap resolution (required only in physical standby server). DB_FILE_NAME_CONVERT=  It is required when directory structure is needed to be in the different datafile. LOG_FILE_NAME_CONVERT=     It is required when directory structure is needed to be in the different logfile. STANDBY_FILE_MANAGEMENT=  It helps to create the file automatically on the standby server. In this demonstration, I am using the below