Skip to main content

STEPS TO TURN ON PHISICAL STANBY TO ACTIVE STANDBY DATABASE



Please follow below steps.

NOTE: Here primary & standby already configuared. The below are the steps we are performing on standby database, to make it active standby database.

-------------------------------------------------------------
1. Connect to the standby database.
-------------------------------------------------------------
2. Stop redo apply using the below script

SQL>recover managed standby database cancel;
---------------------------------------------------------------------------------------------------
3. Issue the following query to find out if the standby database is performing Redo Apply or real-time apply. If the MRP0 or MRP process exists, then the standby database is applying redo

SQL> SELECT PROCESS, STATUS FROM V$MANAGED_STANDBY;

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

4. Check database tole, open mode using the below script. 

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

NAME      DATABASE_ROLE        OPEN_MODE
---------     ------------------------------   ------------------
TESTP     PHYSICAL STANDBY      MOUNTED  

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

5. Now open the database in OPEN READ ONLY mode. Use below SQL

SQL> Alter database open read only;

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

6. Check database tole, open mode using the below script. 

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

NAME      DATABASE_ROLE       OPEN_MODE
---------     ------------------------------   ------------------
TESTP    PHYSICAL STANDBY     READ ONLY

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

7. start redo apply using below SQL on standby database.

SQL>alter database recover managed standby database using current logfile disconnect;

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

8. Check database tole, open mode using the below script. 

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

NAME      DATABASE_ROLE       OPEN_MODE
----------    -----------------------------    -----------------------------------
TESTP    PHYSICAL STANDBY     READ ONLY WITH APPLY

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


NOTE:

--------------------------------------------
Start Redo Apply or Real-Time Apply:
--------------------------------------------

- To start Redo Apply, issue the following statement: - 

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;


- To start real-time apply, issue the following statement: - 

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;


Labels:

Comments

Post a Comment

Popular posts from this blog

ORA-28007: THE PASSWORD CANNOT NE REUSED

             - Here will see how to deal with  => ORA-28007: the password cannot be reused -  I got a request from client user, stating his account has been locked. When I check the status of the account I found the below. connect to SYS user & execute the below query of that database. SQL> select password,username,account_status,profile from dba_users where username='TEST'; PASSWORD               USERNAME   ACCOUNT_STATUS                 PROFILE ------------------             ----------------  -------------------------------           -------------------- AB2Aa8AC9971521e3     TEST       EXPIRED(GRACE)&LOCKED    NONAPP_USERS So, then I have unlocked the account and checked the same again & I found the below results. ...
Post a Comment
Read more

ORA-39014: One or more workers have prematurely exited.ORA-00018: maximum number of sessions exceeded

ERROR: I was Performing a full database import and during the import I faced the below error. ORA-39014: One or more workers have prematurely exited. ORA-39029: worker 6 with process name "DW07" prematurely terminated ORA-31672: Worker process DW07 died unexpectedly. Job "SYSTEM"."SYS_IMPORT_FULL_04" stopped due to fatal error at 00:59:40 ORA-39014: One or more workers have prematurely exited. SOLUTION:  Run the import with fewer parallel processes, like PARALLEL=2 instead of 8. I was able to run the import successfully. NOTE 1: This errors occurs when there are less session allocation in the database. check the session,process parameters and increase them accordingly. To avoid such errors again. NOTE 2 : Note: Increasing processes parameter increases the amount of shared memory that needs to be reserved & the OS must be configured to support the larger amount of shared memory. So here we first need to increase the Memory & SG...
Post a Comment
Read more