DOYENSYS Knowledge Portal




We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal




Tuesday, September 29, 2015

HOW TO REMOVE A DATA GUARD BROKER CONFIGURATION

We know if dg_broker_start parameter is set to TRUE means data guard configuration information contains in broker configuration files dg_broker_config_file1,dg_broker_config_file2 with broker-managed Data Guard Configuration.

Step 1 : Check the existing DGMGRL configuration status , archive destination details & broker status as below,

DGMGRL> show configuration
Configuration - dg

  Protection Mode: MaxPerformance
  Databases:
    admdb - Primary database
    stldb - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS

Archive log destinations like as

SQL>  show parameter log_archive_dest_

NAME                 TYPE       VALUE
-------------------- ----------- -------------
log_archive_dest_1  string     location=USE_DB_RECOVERY_FILE_
                               DEST, valid_for=(ALL_LOGFILES,
                               ALL_ROLES)

log_archive_dest_2  string     service="stldb", LGWR ASYNC NO
                               AFFIRM delay=0 optional compre
                               ssion=disable max_failure=0 ma
                               x_connections=1 reopen=300 db_
                               unique_name="stldb" net_timeou
                               t=30, valid_for=(all_logfiles,
                               primary_role)

SQL> select name , value from v$parameter where name like '%dg_broker%';

NAME                       VALUE
-----------------------------------------------------------------
dg_broker_start            TRUE

dg_broker_config_file1     /u01/app/oracle/product/11.2.0/dbhome/dbs/dr1admdb.dat

dg_broker_config_file2     /u01/app/oracle/product/11.2.0/dbhome/dbs/

2. Remove data guard configuration with Data Guard Manager Command Line - DGMGRL use remove configuration

Connect to Primary database with DGMGRL with SYS user and use command

DGMGRL> remove configuration
Removed configuration

DGMGRL> show configuration
ORA-16532: Data Guard broker configuration does not exist


Configuration details cannot be determined by DGMGRL

3. On the primary database set dg_broker_start parameter FALSE


SQL> alter system set dg_broker_start=FALSE;

System altered.

select name , value from v$parameter where name like '%dg_broker%';
NAME                       VALUE
-----------------------------------------------------------------
dg_broker_start          FALSE
dg_broker_config_file1  /u01/app/oracle/product/11.2.0/dbhome/dbs/dr1admdb.dat
dg_broker_config_file2  /u01/app/oracle/product/11.2.0/dbhome/dbs/dr2admdb.dat

4. When we are remove configuration on DGMGRL, then archive destination for service cleared automatically.

SQL> show parameter log_archive_dest

NAME                 TYPE       VALUE
-------------------- ----------- -------------
log_archive_dest_1  string     location=USE_DB_RECOVERY_FILE_
                               DEST, valid_for=(ALL_LOGFILES,
                               ALL_ROLES)

log_archive_dest_2  string     

5. On standby disable data guard broker

SQL>alter system set dg_broker_start=FALSE;

System altered.

select name , value from v$parameter where name like '%dg_broker%';
NAME                       VALUE
-----------------------------------------------------------------
dg_broker_start          FALSE
dg_broker_config_file1  /u01/app/oracle/product/11.2.0/dbhome/dbs/dr1admdb.dat
dg_broker_config_file2  /u01/app/oracle/product/11.2.0/dbhome/dbs/dr2admdb.dat

6. On primary and standby database move broker configuration files.

[oracle@oel62-x64 dbs]$ ls -l dr*.dat
-rw-r----- 1 oracle oinstall 16384 Jul 16 18:00 dr1admdb.dat
-rw-r----- 1 oracle oinstall 16384 Jul 16 17:59 dr2admdb.dat

[oracle@oel62-x64 dbs]$ mv dr1admdb.dat dr1admdb.dat.bak
[oracle@oel62-x64 dbs]$ mv dr2admdb.dat dr2admdb.dat.bak



No comments: