Active Data Guard is the option when the standby database is configured to be in its status open with read-only mode. As explained below in the white paper “Oracle (Active) Data Guard 19c Real-Time Data Protection and Availability,” there are some benefits, dated March 2019:
With this in mind, the current post is about enabling your Physical Standby database as an Active Data Guard. Taking as a primary step that you already have a configured Physical Standby database, this post follows the procedures below:
- CANCEL the current managed recovery in the Physical Standby database;
- STOP the Physical Standby database (if Oracle RAC, shutdown in all nodes);
- START the Physical Standby database in MOUNTED state (if Oracle RAC, start in all nodes);
- OPEN the Physical Standby database (if Oracle RAC, shutdown in all nodes);
- ENABLE managed recovery in the Physical Standby database;
All these steps mentioned above, except the shutdown part, it is shown in the example below:
-- STARTING FROM step "START the Physical Standby database in MOUNTED state (if Oracle RAC, start in all nodes);" SQL> conn /as sysdba Connected. SQL> alter database recover managed standby database cancel; Database altered. SQL> alter database open; Database altered. SQL> alter database recover managed standby database using current logfile disconnect from session; Database altered. SQL> select name,open_mode from v$database; NAME OPEN_MODE --------- -------------------- TECHDB1 READ ONLY WITH APPLY SQL> select process,status,sequence# from v$managed_standby; PROCESS STATUS SEQUENCE# --------- ------------ ---------- DGRD ALLOCATED 0 ARCH CLOSING 292859 DGRD ALLOCATED 0 ARCH CLOSING 311792 ARCH CLOSING 292860 ARCH CLOSING 311791 RFS IDLE 292861 MRP0 APPLYING_LOG 292861 RFS IDLE 0 RFS IDLE 0 RFS IDLE 311793 11 rows selected. SQL> conn /as sysdba Connected. SQL> select name,open_mode from v$database; NAME OPEN_MODE --------- -------------------- TECHDB1 MOUNTED -- Here it is crucial to verify that all STANDBY database instances are open. Otherwise, only one instance will be behaving as an ACTIVE Data Guard, as in the example below: SQL> select name,open_mode from gv$database; NAME OPEN_MODE --------- -------------------- TECHDB1 MOUNTED TECHDB1 READ ONLY WITH APPLY SQL> alter database recover managed standby database cancel; Database altered. SQL> alter database open; Database altered. SQL> alter database recover managed standby database using current logfile disconnect from session; Database altered. -- All instances of the Oracle RAC Data Guard database are running as an ACTIVE Data Guard: SQL> select name,open_mode from gv$database; NAME OPEN_MODE --------- -------------------- TECHDB1 READ ONLY WITH APPLY TECHDB1 READ ONLY WITH APPLY SQL> select process,status,sequence# from v$managed_standby; PROCESS STATUS SEQUENCE# --------- ------------ ---------- ARCH CONNECTED 0 DGRD ALLOCATED 0 DGRD ALLOCATED 0 ARCH CONNECTED 0 ARCH CONNECTED 0 ARCH CONNECTED 0 MRP0 APPLYING_LOG 292862 7 rows selected.
*The views expressed here are my own and do not represent those of my employer.*
Hello, I’m Bruno — a dual citizen of Brazil and Sweden. I bring a global perspective shaped by experiences in both South America and Europe, with a strong focus on collaboration and innovation across cultures. I am a Computer Scientist, PhD Candidate in Information and Communication Technologies, focusing on Data Science and Artificial Intelligence, and hold dual Master’s degrees in Data Science and Cybersecurity. With over fifteen years of international experience spanning Brazil, Hungary, and Sweden, I have collaborated with global organizations such as IBM, Playtech, and Oracle, as well as contributed remotely to projects across multiple regions. My professional interests include Databases, Cybersecurity, Cloud Computing, Data Science, Data Engineering, Big Data, Artificial Intelligence, Programming, and Software Engineering, all driven by a deep passion for transforming data into strategic business value.