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;


Comments

Popular posts from this blog

Registering The Database to RMAN catalog database:

Registering The Database to RMAN catalog database: Need to start RMAN as follows: RMAN target=sys/password@database_to_backup rcvcat=sys/password@recovery_catalog_database Another variation on the command, if the recovery catalog and the database were on the same server, might be as shown: oraenv ORACLE_SID = [KKUY] ? KKUY RMAN rcvcat=sys/password@recovery_catalog_database RMAN> connect target Recovery Manager: Release 8.0.5.1.0 - Production RMAN-06005: connected to target database: KKUY RMAN-06008: connected to recovery catalog database Use the below command to register the database. RMAN>register database; Want to verify if a database is registered in the recovery catalog. To do this, connect to RMAN and issue the command LIST INCARNATION OF DATABASE. RMAN> list incarnation of database; RMAN-03022: compiling command: list RMAN-06240: List of Database Incarnations RMAN-06241: DB Key Inc Key DB Name DB ID      CUR Reset SCN   Reset Time RMAN

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