Oracle 11g Physical standby data Guard Failover steps

-

Oracle 11g Physical standby data Guard Failover steps

In case of worst situation with data guard primary database, or not available for production than we can activated standby database as a primary production database.

 standby Database:

 Verify database name its open mode and its role from following SQL command:


SQL> select name,open_mode,database_role from v$database; 
NAME OPEN_MODE DATABASE_ROLE 
--------- -------------------- ---------------- 
RTS MOUNTED PHYSICAL STANDBY


 Following sort of SQL command will help to bring up standby as primary:


SQL> alter database recover managed standby database finish; Database altered.




SQL> alter database activate standby database; Database altered.



Managed recovery process has been stopped between primary and standby database and standby becomes primary database.



Bounce your database and verify database name its open mode and its role:






SQL> shutdown immediate; ORA-01109: 


database not open Database dismounted. 


ORACLE instance shut down.




SQL> startup ORACLE instance started. 




Total System Global Area 1469792256 bytes Fixed Size 2213456 bytes Variable Size 905972144 bytes Database Buffers 553648128 bytes Redo Buffers 7958528 bytes Database mounted. Database opened.




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






NAME OPEN_MODE DATABASE_ROLE 


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


RTS READ WRITE PRIMARY



Note:



Now
 your old standby database is become primary database, it is highly 
recommended to consider immediate full backup of primary database.






































Comments











Post a Comment



















Popular posts from this blog









RAC Failure Scenario - Testing in our RAC Test DB - Node 1 & Node 2






-















 RAC Failure Scenario - Testing in our RAC Test DB - Node 1 & Node 2   Testing Various RAC Failure scenario like:   1 - Node Failure  2 - DB Instance Failure  3 - ASM Instance Failure  4 - Listener failure  5 - Public Network Failure  6 - Private Network Failure  7 - OCR & Voting Disk Failure  8 - ASM Disk Failure   ==============  1 - Node Failure   ==============  It can be planned, unplanned or all the nodes it could be any scenario   Let us start the workload & shutdown the node   The expected result will be:   Resources will go offline  Instance recovery will be performed  Node vip & scan vip fail to surviving node  Scan listener will fail over surviving node  Client connection are moved to surviving instance   Now shutdown Node 1 in OS Level intentionally or due to some reason the node 1 is shutdown   #Shutdown –h now   Check the node 2 status   [oracle@test-rac2 ~]$ crs_stat -t   Name           Type           Target    State     Host  ----------------------------








Read more










ORA-01110: data file 1: '/oradata/datafiles/system01.dbf'






-















  ORA-01110: data file 1: '/oradata/datafiles/system01.dbf'    Error occur while restoring the database from the backup of RMAN   RMAN> alter database open resetlogs;   using target database control file instead of recovery catalog   RMAN-00571: ===========================================================  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============  RMAN-00571: ===========================================================  RMAN-03002: failure of alter db command at 09/03/2017 16:05:14  ORA-01194: file 1 needs more recovery to be consistent  ORA-01110: data file 1: '/oradata/datafiles/system01.dbf'   To resolve this error fallow the below procedure – Hopefully you will succeed   If you’re primary database is flashback & it has the standby – Fallow below procedure   RMAN> run {  2> recover database;  3> }   ORA-00283: recovery session canceled due to errors   RMAN-11003: failure during parse/execution of SQL statement: alter datab








Read more










Expdp from Higher version 12c (12.1.0.2) to lower version 11g (11.2.0.4)






-















                                                                     Expdp from Higher version 12c (12.1.0.2) to lower version 11g (11.2.0.4)     Export on 12c (12.1.0.2)   – Tested in our env : 10.20.0.82     ====================   SQL> select instance_name,version from v$instance;   INSTANCE_NAME    VERSION  ---------------- -----------------  ora12c           12.1.0.2.0   SQL> conn sys/sys as sysdba  Connected.   SQL> conn hassan/( password );  Connected.   SQL> select table_name from user_tables;   TABLE_NAME  --------------------------------------------------------------------------------  TEST   SQL> select * from test;   COLUMN1              NAME  -------------------- --------------------  1                    abc  2                    xyz   [oracle@ora12c u02]$ mkdir dump   [oracle@ora12c u02]$ chmod -R 777 dump/   [oracle@ora12c u02]$ sqlplus / as sysdba   SQL*Plus: Release 12.1.0.2.0 Production on Wed Jan 25 16:22:46 2017  Copyright (c) 1982, 2014, Oracle.  All








Read more