Skip to main content

How to perform Oracle 11g Data Guard Switchover and Switchback

 How to perform Oracle 11g Data Guard Switchover and Switchback 


Switchover:


Before performing switchover, please  verify the state of the data guard on both the instances by following SQL queries:


 SQL> ALTER SESSION SET nls_date_format='DD-MON-YYYY HH24:MI:SS';

 SQL> SELECT sequence#, first_time, next_time, applied

 FROM v$archived_log

 ORDER BY sequence#;


 

 SQL> select dest_name,status,error from v$archive_dest where dest_name='LOG_ARCHIVE_DEST_2';

 DEST_NAME

 --------------------------------------------------------------------------------

 STATUS ERROR

 --------- -----------------------------------------------------------------

 LOG_ARCHIVE_DEST_2

 VALID


 SQL> select message from v$dataguard_status;


Note: This command will give you an appropriate message about the data guard current status.


Kick-Off switchover activity by issuing the following  commands:


On Primary database:


Step-1

Connect to Primary database and convert primary database to standby.


 [oracle@funoracle ~]$ sqlplus / as sysdba

 SQL> alter database commit to switchover to standby;

 Database altered.


Step-2

Shutdown primary database:


SQL> shutdown immediate;


Step-3


Startup nomount old primary database as new standby database:


 SQL> startup nomount

 ORACLE instance started.

 

 

 SQL> alter database mount standby database;

 Database altered.

 SQL> alter database recover managed standby database disconnect from session;

 Database altered.


Verify database role on old primary database:


 SQL> select name,open_mode,database_role from v$database;

 NAME OPEN_MODE DATABASE_ROLE

 --------- -------------------- ----------------

 PROD MOUNTED PHYSICAL STANDBY

 


On Standby database:


Step-4

On the original standby database, Convert the old standby database to the primary database:

 SQL> alter database commit to switchover to primary;

 Database altered.


Step-5


Convert old standby database as primary and shutdown database:


[oracle@funoracledr ~]$ sqlplus / as sysdba


 SQL> shutdown immediate;

 ORA-01109: database not open

 Database dismounted.

 ORACLE instance shut down.


Step-6


Startup old standby database as the primary database:


 SQL> startup

 ORACLE instance started.

 

Verify database role on old standby database:


 SQL> select name,open_mode,database_role from v$database;

 NAME OPEN_MODE DATABASE_ROLE

 --------- -------------------- ----------------

 PROD READ WRITE PRIMARY


Switch overactivity have completed successfully, our old primary database has become standby and old standby database has become the primary database.


Note

We can test the above switchover activity, by generating multiple archive logs on the primary database and verify those archive logs being transferred on the standby database.


Switchback:

To switchback, we  have to follow the same above-mentioned steps

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

EBS 12.2 ADOP Interview Questions With Scenarios

EBS 12.2 ADOP Interview Questions With Scenarios Note: Check the patch cycle log is important to fix any issues.  Location: $ADOP_LOG_HOME Useful Adop Commands Click here 1.What is ADOP concept in oracle apps Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. 'adop' is the utility we use to apply patches in R12.2 2.What is PATCH_TOP directory in R12.2 In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to $NE_BASE/EBSapps/patch $NE_BASE points to <Non-Editioned-filesystem-directory> Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files. If you are planning to put patches in non-defualt location then you need to use adop parameter 'patchtop=<patch_path>' to...