How to remove database from Data Guard Configuration

-

 On Primary:

No
Step
Details / Screnshot
1
Login to dgmgrl
dgmgrl
2
Connect to Primary Database
connect sys/abc123@MoidPR
3
Check Configuration
show configuration


DGMGRL> show configuration

Configuration
 Name:             broker
 Enabled:          YES
 Protection Mode: MaxPerformance
 Fast-Start Failover: DISABLED
 Databases:
MoidPR - Primary database
MoidDG - Physical standby database

Current status for "broker":
SUCCESS
4
Remove configuration
remove configuration

DGMGRL> remove configuration
Removed configuration
5
Exit out of dgmgrl
exit
6
Set oracle environment to Primary Database
. oraenv → MoidPR
7
Login as sys
sqlplus / as sysdba
8
Find out where archives writing to locally?
show parameter log_archive_dest_1
9
Find out where archives write to remotely?
show parameter log_archive_dest_2
10
Verify dg_broker is set to TRUE
select
name ,
value
from
v$parameter
where
name like '%dg_broker%';
11
Turn DG_BROKER to FALSE
alter system set dg_broker_start=FALSE;

SQL> alter system set dg_broker_start=FALSE;

System altered.
12
Verify LOG_ARCHIVE_DEST_2 is removed.
show parameter log_archive_dest_2
13
exit ot of SQL
exit;


On standby:
No
Step
Details / Screnshot
1
SEt oracle environment to Standby Database.
. oraenv → MoidDG
2
Login as sys
sqlplus / as sysdba
3
Set DG_BROKER to FALSE
alter system set dg_broker_start=FALSE;


SQL> alter system set dg_broker_start=FALSE;

System altered.

Optionally: On Primary and Standby
No
Step
Details / Screnshot
1
Find where the .dat files are remove them
show parameter dg_broker_config_file1
show parameter dg_broker_config_file2

NAME    TYPE VALUE
------------------------ -------  ----
dg_broker_config_file1   string /u01/app/oracle/product/11.2.0/db_1/dbs/dr1MoidPR.dat

dg_broker_config_file1   string /u01/app/oracle/product/11.2.0/db_1/dbs/dr1MoidDG.dat
2
Move the Data Broker Files
cd $ORACLE_HOME/dbs
mv MoidPR.dat dr1MoidPR.dat.bak
mv MoidDG.dat dr2MoidDG.dat.bak

Hope this helps.

Comments

Post a Comment

Popular posts from this blog

Step by Step: How to troubleshoot a slow running query in Oracle

-
This is a day to day task of a DBA. Someone from application team comes to our desk and simply says a query is running slow. We may question him on many things but ultimately a DBA has to tune the query at the end. This is also very popular and known question for the DBA's who are attending interviews. This question is simply asked again and again. I have also been asked this question multiple times. After a pause, interviewer simply asks...so suppose a user comes and reports that his query is running slow, what will be your approach to tune this. There is no absolute or concrete answer to this question because there might be multiple way to tune a slow running query. Everyone can have a different approach. So here is my approach: Very first thing we have to find which type of query is running slow. Whether it is SELECT query of DML statements(insert, update, delete and merge). So first we will see how to tune a SELECT query Step 1 – Find the SQL_ID of the
Read more

Register Archive log file manually in standby Database

-
  Some time, the archive logs are not shipping to standby location due to network issue.  There may be  several  archive logs are waiting in standby location for one archive log file. For instance, Archive log sequence # 100 is not shipped to standby location. But other archive logs(sequence#101 to sequence#200) were shipped to standby and it is waiting to ship the sequence# 100.  In this scenario, DBA can copy the archive log file and register manually. Once manually registered, the sequence#101 to sequence#200 will apply automatically on standby database. Step 1 Let us assume, the archive log file devdb12_1_283_801988635.arc is not shipped to standby due to some reason. Copy the archive log file devdb12_1_283_801988635.arc manually from primary to standby archive destination location. Step  2 Run the below command in standby database. ALTER DATABASE REGISTER LOGFILE '/dbArch/oradata/devdb12/ devdb12_1_283_801988635.arc';   Step  3 Verify the standby database and see if the co
Read more

How to check UNDO tablespace usage and who is using more undo

-
Query To check UNDO tablespace usage: ================================ set linesize 152 col tablespace_name for a20 col status for a10 select tablespace_name,status,count(extent_id) "Extent Count", sum(blocks) "Total Blocks",sum(bytes)/(1024*1024*1024) spaceInGB from   dba_undo_extents group by  tablespace_name, status having tablespace_name=upper('&TSNAME') order by tablespace_name; Query To check who is using more UNDO space: ===================================== SET termout ON SET heading ON SET PAGESIZE   6000 SET LINESIZE   200 COLUMN pgm_notes    FORMAT a80        HEADING 'Notes' COLUMN rbs          FORMAT a16         HEADING 'RBS'             JUST center COLUMN oracle_user  FORMAT a12        HEADING 'Oracle|Username' COLUMN sid_serial   FORMAT a12        HEADING 'SID,Serial' COLUMN unix_pid     FORMAT a6         HEADING 'O/S|PID' COLUMN Client_User  FORMAT a14        HEADING 'Cl
Read more