Change Protection Mode for Active Dataguard (11GR2)

Change Protection Mode for Active Dataguard (11GR2)

Primary Database :  TESTDB
Standby Database :  TESTDBDR
Database version   :  11gR2
 The database is running under Maximum Performance mode.
SQL> select status,instance_name,database_role,protection_mode from v$database,v$instance;

STATUS INSTANCE_NAME DATABASE_ROLE PROTECTION_MODE
------ ------------- ------------- --------------------
OPEN   TESTDB        PRIMARY       MAXIMUM PERFORMANCE

In order to change the protection mode to either MAXIMUM AVAILABILITY/MAXIMUM PROTECTION, we need to have the standby redo logs configured on
the standby database. Also, the redo shippment parameter (log_archive_dest_2) on the primary database should be configured to use SYNCHRONOUS
(“SYNC”) mode.
Let’s check the number of online redo logs and it’s size on primary database
SQL> select group#,bytes/1024/1024 from v$log;

GROUP# BYTES/1024/1024
------ ------------------
1      512
2      512
It can be noticed from below that there are no standby redo log groups configured on the primary database.
SQL> select group#,bytes/1024/1024 from v$standby_log;

no rows selected
Add standby redo log groups on the primary database with the same size as that of the online redo log groups.
SQL> alter database add standby logfile group 4 size 512M;

Database altered.

SQL> alter database add standby logfile group 5 size 512M;

Database altered.

SQL> alter database add standby logfile group 6 size 512M;

Database altered.

SQL> alter database add standby logfile group 7 size 512M;

Database altered.
We can now notice that 4 standby redo log groups have been added with the same size as that of the online redo logs.
These standby redo logs will not be used on the primary database and will be used only when a switchover takes place.
SQL> select group#,bytes/1024/1024 from v$standby_log;

GROUP# BYTES/1024/1024
------ ---------------
4      512
5      512
6      512
7      512

SQL> select thread#,max(sequence#) from v$archived_log group bythread#;

THREAD# MAX(SEQUENCE#)
------- --------------
1       311
Standby:
SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;

THREAD# MAX(SEQUENCE#)
------- --------------
1       311
Standby database is in sync with the primary database.
Standby database details:
SQL> select status,instance_name,database_role from v$database,v$Instance;

STATUS  INSTANCE_NAME DATABASE_ROLE
------- ------------- ------------------
MOUNTED TESTDBDR        PHYSICAL STANDBY
On the standby database, there are 3 online redo log groups with the size 512M and there are no standby redo log groups.
SQL> select group#,bytes/1024/1024 from v$log;

GROUP# BYTES/1024/1024
------ ----------------
1      512
3      512
2      512

SQL> select group#,bytes/1024/1024 from v$standby_log;

no rows selected
Let’s add standby redo log groups on the standby database but before that, we need to check if MRP (Managed Recovery Process) is running on
the standby database and if running, then it needs to be cancelled.
SQL> select process,status,sequence# from v$managed_standby;

PROCESS STATUS       SEQUENCE#
------- ------------ ----------
ARCH    CONNECTED    0
ARCH    CONNECTED    0
ARCH    CONNECTED    0
ARCH    CONNECTED    0
RFS     IDLE         0
RFS     IDLE         0
RFS     IDLE         0
MRP0    WAIT_FOR_LOG 312

8 rows selected.
Cancel the MRP process on the standby database:
SQL> alter database recover managed standby database cancel;

Database altered.
Add 4 Standby Redo Log (SRL) groups of size same as online redo log groups (512M) on the standby database:
SQL> alter database add standby logfile group 4 size 512M;

Database altered.

SQL> alter database add standby logfile group 5 size 512M;

Database altered.

SQL> alter database add standby logfile group 6 size 512M;

Database altered.

SQL> alter database add standby logfile group 7 size 512M;

Database altered.

SQL> select group#,bytes/1024/1024 from v$standby_log;

GROUP# BYTES/1024/1024
------ ---------------
4      512
5      512
6      512
7      512
once the SRLs are added, start the MRP on the standby database
SQL> alter database recover managed standby database disconnectfrom session;

Database altered.

SQL> select process,status,sequence# from v$managed_standby;

PROCESS STATUS       SEQUENCE#
------- -----------  ----------
ARCH    CONNECTED    0
ARCH    CONNECTED    0
ARCH    CONNECTED    0
ARCH    CONNECTED    0
RFS     IDLE         0
RFS     IDLE         0
RFS     IDLE         0
MRP0    WAIT_FOR_LOG 312

8 rows selected.
As said earlier, configure the redo shippment parameter (log_archive_dest_2) on the primary database to use SYNCHRONOUS mode.
Primary database:
SQL> show parameter log_archive_dest_2

NAME               TYPE   VALUE
------------------ ------ -----------------------------------
log_archive_dest_2 string service=TESTDBDR valid_for=(online_logf                          iles,primary_role) db_unique_name=srp                          stb

SQL> alter system set log_archive_dest_2='service=TESTDBDR LGWR AFFIRM SYNC valid_for=(online_logfiles,primary_role) db_unique_name=TESTDBDR';

System altered.

SQL> show parameter dest_2

NAME                        TYPE   VALUE
--------------------------- ------ ----------------------------
db_create_online_log_dest_2 string
log_archive_dest_2          string service=TESTDBDR LGWR AFFIRM                              SYNC valid_for=(online_logfiles,p
                            rimary_role) db_unique_name=TESTDBDR
shutdown the primary database and mount it.
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.

Total System Global Area 208769024 bytes
Fixed Size 2226936 bytes
Variable Size 180356360 bytes
Database Buffers 20971520 bytes
Redo Buffers 5214208 bytes
Database mounted.
SQL>
Now change the protection mode on the primary database according to the requirement using the below command
“alter database set standby database to maximize {AVAILABILITY | PROTECTION| PERFORMANCE}”
Here, I am changing the protection mode from MAXIMUM PERFORMANCE to MAXIMUM AVAILABILITY
SQL> alter database set standby database to maximize availability;

Database altered.
Once the mode is changed, open the primary database and verify the same.
SQL> alter database open;

Database altered.

SQL> select status,instance_name,database_role,protection_mode from v$database,v$instance;

STATUS INSTANCE_NAME DATABASE_ROLE PROTECTION_MODE
------ ------------- ------------- ----------------------
OPEN   TESTDB        PRIMARY       MAXIMUM AVAILABILITY
check if the standby database is in sync with the primary database
On primary:
SQL> select thread#,max(sequence#) from v$archived_log group bythread#;

THREAD# MAX(SEQUENCE#)
------- --------------
1       316
Standby:
SQL> select status,instance_name,database_role,protection_mode from v$database,v$instance;

STATUS  INSTANCE_NAME DATABASE_ROLE    PROTECTION_MODE
------- ------------- ---------------- --------------------
MOUNTED TESTDBDR        PHYSICAL STANDBY MAXIMUM AVAILABILITY

SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;

THREAD# MAX(SEQUENCE#)
------- --------------
 1      316
standby database is in sync with the primary and also the PROTECTION mode has been changed to MAXIMUM AVAILABILITY.
Here we go !!



Comments

Post a Comment

Popular posts from this blog

AWR Reports

AWR Reports Introduction Workload Repository Reports AWR Snapshots and Baselines Moving AWR Information Reading the AWR Report Useful Queries Remove and Disable AWR Links with AWR Analyzer Introduction AWR periodically gathers and stores system activity and workload data which is then analyzed by ADDM. Every layer of Oracle is equipped with instrumentation that gathers information on workload which will then be used to make self-managing decisions. AWR is the place where this data is stored. AWR looks periodically at the system performance (by default every 60 minutes) and stores the information found (by default up to 7 days). AWR runs by default and Oracle states that it does not add a noticeable level of overhead. A new background server process (MMON) takes snapshots of the in-memory database statistics (much like STATSPACK) and stores this information in the repository. MMON also provides Oracle10G with a server initiated alert feature, which notifies database admini
Read more

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

QL> startup ORA-01261: Parameter db_recovery_file_dest destination string cannot be translated SQL> create pfile from spfile; create pfile from spfile * ERROR at line 1: ORA-01565: error in identifying file '?/dbs/spfile@.ora' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3   SQL> shut abort SQL> create pfile='/home/oracle/initORA11G.ora' from spfile='+DATA/ORA11G/spfileORA11G.ora'; File created. oracle@rac1.localdomain:/home/oracle [ORA11G1] >dba SQL*Plus: Release 11.2.0.3.0 Production on Wed Apr 6 20:15:29 2016 Copyright (c) 1982, 2011, Oracle.  All rights reserved. Connected to an idle instance. SQL> startup pfile='/home/oracle/initORA11G.ora'; ORACLE instance started. Total System Global Area 1653518336 bytes Fixed Size                  2228904 bytes Variable Size             956304728 bytes Database Buf
Read more

My Fav Song in Telugu: Aa challani samudra garbham

Image
                                                                                                          ఆ చల్లని సముద్ర గర్భం దాచిన బడబానలమెంతో  ఆ నల్లని ఆకాశంలో కానరాని భాస్కరులెందరో  ||ఆ చల్లని|| భూగోళం పుట్టుక కోసం రాలిన సుర గోళాలెన్నో  ఈ మానవ రూపం కోసం జరిగిన పరిణామాలెన్నో ఒక రాజుని గెలిపించుటలో ఒరిగిన నర కంఠములెన్నో కుల మతాల సుడిగుండాలకు బలియైన పవిత్రులెందరో  ||ఆ చల్లని|| మానవ కళ్యాణం కోసం పణమెత్తిన రక్తము ఎంతో  రణరక్కసి కరాళ నృత్యం రాచిన పసి ప్రాణాలెన్నో కడుపు కోతతో అల్లాడిన కన్నులలో విషాదమెంతో  భూస్వాముల  దౌర్జన్యాలకు  ధనవంతుల దుర్మార్గాలకు  దగ్ధమైన బతుకులు ఎన్నో  ||ఆ చల్లని|| అన్నార్తులు అనాథలుండని ఆ నవయుగమదెంత దూరం  కరువంటూ కాటకమంటూ కనిపించని కాలాలెపుడో పసిపాపల నిదుర కనులలో ముసిరిన భవితవ్యం ఎంతో  గాయపడిన కవి గుండెలలో రాయబడని కావ్యాలెన్నో ||ఆ చల్లని || a challani samudra garbham daachina badabaanalamentho  Aa nallani aakasamlo kanarani bhaskarulendharoooo || Aa Challani ||  Bhoogolam puttuka kosam raalina sura golaalenno Eee manava rupam kosam jarigina parin
Read more