Configure Active DataGuard and DG BROKER

 Oracle Active Data Guard allows DBAs and users to run real-time queries on a physical standby system for reporting.

Queries and reports can be offloaded from the production system to a synchronized physical standby database – all queries at the standby database return up-to-date results.

1. Make sure archive log enabled in primary database.

2. Enabled forced logging and try to switch logfile

The DB_UNIQUE_NAME values of the primary and standby database should be used in the DG_CONFIG setting of the LOG_ARCHIVE_CONFIG parameter. For this example, the standby database will have the value “TESTDB_DG”.

3. Set suitable remote archive log destinations for both the database

4. The LOG_ARCHIVE_FORMAT and LOG_ARCHIVE_MAX_PROCESSES parameters must be set to appropriate values and the REMOTE_LOGIN_PASSWORDFILE must be set to exclusive

5. Set the parameter in primary database

6. Entries for the primary and standby databases in “$ORACLE_HOME/network/admin/tnsnames.ora” files on both servers

7. Create standby Control file and PFILE

8. Change the necessary parameter according to Standby Database

Step for Standby Database preparation
1. Create the necessary directories on the standby server

2. Copy password file from primary to standby database

3. Create standby database using DUPLICATE command

4. Connect to RMAN, specifying a full connect string for both the TARGET and AUXILIARY instances

5. Switch standby database to Read only mode

6. Start MRP process in standby database

Enable DATAGUARD BROKER
1. Connect to both databases (primary and standby) and issue the following command

2. Check configuration and status of the databases from the broker

3. Switch over and Fail over database using DATAGUARD broker

Comments

Popular posts from this blog

ORA-01565: error in identifying file '?/dbs/spfile@.ora'

Reboot Exadata Machine

How to combine Oracle .ova files