Switchover/Failover to physical standby

Hi All,
I have dataguard configured between Primary and physical standby. I would like to know how can i switch over to physical stanby when the network link is down between primary and physical standby.
I mean what steps I can follow to make physical standby to primary and primary to staandby even when the network connectivity is down between them.
Regards,
Raj

user12263161 wrote:
Hi All,
I have dataguard configured between Primary and physical standby. I would like to know how can i switch over to physical stanby when the network link is down between primary and physical standby. You can only failover in this case, but, if you have flashback on, you can reinstate ex-Primary to standby like described [url http://nikolayivankin.wordpress.com/2012/02/14/dgmgrl-reinstating-ex-primary-to-standby-by-flashback-database-feature/]here

Similar Messages

Switchover to a Physical Standby Database

Hello all,
i have completed Switchover to a Physical Standby Database succesfully, there is no error in alter log file but when i fire on my new primary database " select * from dba_segments order by 2" then it give me following error
SQL Error: ORA-00604: error occurred at recursive SQL level 1
ORA-06553: PLS-801: internal error [56319]
ORA-06544: PL/SQL: internal error, arguments: [56319], [], [], [], [], [], [], []
ORA-06553: PLS-801: internal error [56319]
00604. 00000 - "error occurred at recursive SQL level %s"
*Cause:    An error occurred while processing a recursive SQL statement
(a statement applying to internal dictionary tables).
*Action:   If the situation described in the next error on the stack
can be corrected, do so; otherwise contact Oracle Support.
my database version is
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
Thank You All For Advance Response.

Though this MOS note applies to 10.1, see if it helps,
*ORA-06544: PL/SQL: internal error, arguments: [56319], ORA-06553: PLS-801: internal error [56319]" errors while running catupgrd.sql [ID 863633.1*
HTH
Aman....

Failover To Physical Standby Database

We have 3 node RAC 11.2.0.3 Primary database data guarded to a 3 node RAC 11.2.0.3 Standby database. There is an activity scheduled to perform some of order extracts in the database which is going to result in a lot of changes. Currently the discussion is on whether what should be the quickest way to go back to a point in time before the extract process starts in case of any issues. The options that we are looking at are:
1) Create a guaranteed restore point on both the Primary and Standby and use this to flashback the database (Quick but we have had issues where in the guaranteed restore point still does not guarantee the availability of the flashback logs) - Tested
2) Use RMAN backup from a day before to restore and recover to point in time before the extract process began (Time consuming) - Tested
3) Use export backup to perform a redirected restore i.e import the data from before the extract process (Time consuming) - Tested
4) Create a guaranteed restore point on both Primary and Standby, stop the Redo Apply/Ship at the time we create the guaranteed restore point and at a point we face some issue and need to go back, simply failover to the physical standby database and then reinstate the new standby database - This has not been tested yet but seems a viable option
With regard to the point 4, note that we are not concerned about data loss as the whole point of stopping the redo apply is to prevent the standby to be caught up with Primary during the run of the extract process. The question is whether the dataguard broker will allow failover of the primary to standby, in a situation described in bullet point 4). Please advice.

HI,
Please check this link:
Physical Standby Database SWITCHOVER &amp; FAILOVER Operations | Talip Hakan Ozturk&#039;s ORACLE BLOG
Thank you

Failover to Physical Standby

Hi All,
I have a configured data guard in my local system . Please find the below configuration of the Data guard
Data Guard Type : - Physical Standby (Oracle version 11g)
Service Responsible for Log Transport : - ARCH
No Standby Redo log : - Neither in Primary Nor in Standby
I am trying to fail over by using command "alter database recover managed standby database finish"
Please find the below alert log info after this command .
Tue Dec 03 01:42:14 2013
alter database recover managed standby database finish
Attempt to do a Terminal Recovery (PRD)
Media Recovery Start: Managed Standby Recovery (PRD)
Fast Parallel Media Recovery enabled
Managed Standby Recovery not using Real Time Apply
Media Recovery Waiting for thread 1 sequence 145
Terminal Recovery timestamp is '12/03/2013 01:42:15'
Terminal Recovery: applying standby redo logs.
Terminal Recovery: thread 1 seq# 145 redo required
Media Recovery Waiting for thread 1 sequence 145
Terminal Recovery: End-Of-Redo log allocation
Terminal Recovery: standby redo logfile 3 created '/data/PRD_DR/arch/arch_1_0_831359165.arch'
This standby redo logfile is being created as part of the failover
operation. This standby redo logfile should be deleted after the
switchover to primary operation completes.
Media Recovery Log /data/PRD_DR/arch/arch_1_0_831359165.arch
Terminal Recovery: log 3 reserved for thread 1 sequence 145
Recovery of Online Redo Log: Thread 1 Group 3 Seq 145 Reading mem 0
Mem# 0: /data/PRD_DR/arch/arch_1_0_831359165.arch
Identified End-Of-Redo for thread 1 sequence 145
Incomplete recovery applied all redo ever generated.
Recovery completed through change 559773 time 11/23/2013 13:38:13
Media Recovery Complete (PRD)
Terminal Recovery: successful completion
Resetting standby activation ID 1895332757 (0x70f87b95)
Completed: alter database recover managed standby database finish
Tue Dec 03 01:42:50 2013
alter database commit to switchover to primary
ALTER DATABASE SWITCHOVER TO PRIMARY (PRD)
Maximum wait for role transition is 15 minutes.
Backup controlfile written to trace file /apps/oracle/diag/rdbms/stand/PRD/trace/PRD_ora_9466.trc
tkcrrxms: Killing 3 processes (all RFS)
Standby terminal recovery start SCN: 559772
RESETLOGS after complete recovery through change 559773
Online log /data/PRD_DR/REDOLOG11.LOG: Thread 1 Group 1 was previously cleared
Online log /data/PRD_DR/REDOLOG21.LOG: Thread 1 Group 2 was previously cleared
Standby became primary SCN: 559771
Tue Dec 03 01:42:53 2013
Here my question is , why oracle implicitly creates a standby redo log in Standby database for successful completion of 'alter database recover managed standby database finish'.
Thanks,

Terminal Recovery timestamp is '12/03/2013 01:42:15'
Terminal Recovery: applying standby redo logs.
Terminal Recovery: thread 1 seq# 145 redo required
Media Recovery Waiting for thread 1 sequence 145
Terminal Recovery: End-Of-Redo log allocation
Terminal Recovery: standby redo logfile 3 created '/data/PRD_DR/arch/arch_1_0_831359165.arch'
This standby redo logfile is being created as part of the failover
operation. This standby redo logfile should be deleted after the
switchover to primary operation completes.
Media Recovery Log /data/PRD_DR/arch/arch_1_0_831359165.arch
Terminal Recovery: log 3 reserved for thread 1 sequence 145
Recovery of Online Redo Log: Thread 1 Group 3 Seq 145 Reading mem 0
Mem# 0: /data/PRD_DR/arch/arch_1_0_831359165.arch
Identified End-Of-Redo for thread 1 sequence 145
Looks like, its due to the following bug.
Bug 5889025 : FINISH FAILOVER GENERATES INCORRECT STANDBY REDO LOG.

Status of Logical Standby In case of Failover to Physical Standby

I am using oracle 9.2.0.8 database . I have one logical and one physical standby database in place. If I perform failover to my physical standby, will my logical standby still continue to work with new primary database?

Thank you for your kind reply.
I performed failover to my physical standby and now archives are going on my logical standby from new primary but changes are not getting applied on my logical standby database.
when i tried to register the logical logfile from new primary on my logical standby i am getting following error.
SQL> ALTER DATABASE REGISTER LOGICAL LOGFILE 'E:\orcl1\stdb\archives\TESTDBT001S00001.ARC';
ALTER DATABASE REGISTER LOGICAL LOGFILE 'E:\orcl1\stdb\archives\TESTDBT001S00001.ARC'
ERROR at line 1:
ORA-01287: file is from a different database incarnation

Physical standby error

Hi friends,
I configured a physical standby database for my primary database. I am able to switchover successfully to physical standby database. So the roles are now changed. Primary is physucal standby, and physical standby is primary.
Now when Iam switching back (now primary to physical standby), there is error at the physical standby which states media recovery needed. I have checked the archives are present at this location. I tried to recover....but thats not working.
Both the databases are 10.2.0.1.0 on windows platform.
Any comments??

Iam sorry for the delay.... here's the alert log
ORA-16139 signalled during: alter database commit to switchover to primary...
Sat Jun 23 14:55:29 2007
alter database commit to switchover to primary
Sat Jun 23 14:55:32 2007
If media recovery active, switchover will wait for completion
Database not available for switchover
End-Of-REDO archived log file has been received
Archived log files detected beyond End-Of-REDO
Incomplete recovery SCN:0:824807 archive SCN:0:830335
Database not available for switchover
End-Of-REDO archived log file has been received
Archived log files detected beyond End-Of-REDO
Incomplete recovery SCN:0:824807 archive SCN:0:830335
Switchover: Media recovery required - standby not in limbo
ORA-16139 signalled during: alter database commit to switchover to primary...
Sat Jun 23 14:59:26 2007
alter database commit to switchover to primary with session shutdown
Sat Jun 23 14:59:39 2007
If media recovery active, switchover will wait for completion
Database not available for switchover
End-Of-REDO archived log file has been received
Archived log files detected beyond End-Of-REDO
Incomplete recovery SCN:0:824807 archive SCN:0:830335
Database not available for switchover
End-Of-REDO archived log file has been received
Archived log files detected beyond End-Of-REDO
Incomplete recovery SCN:0:824807 archive SCN:0:830335
Switchover: Media recovery required - standby not in limbo
-Nand

Physical Standby DB - failover setup

Can you please help me with the following questions:
1. XELUSP1 is Production database, XELUSS1 is physical standby database for XELUSP1. During XELUSP1 crash, we brought up XELUSS1 as primary database manually. Post XELUSP1 is back to primary, Can we use XELUSS1 as standby database as it was?
2. What are the steps to be done in order to make XELUSS1 as primary during failover scenario from XELUSP1?
3.What is the impact in client/server environment in 1st case? How it can be fixed?

Hi,
1.No, u can't use it again in case of failover but this thing is possible in switchover mode.
2.diff commands for diff oracle version.tell me on which version u want to perform it.
3.littile downtime when role of server becomes changing.
Thanks
Kuljeet

Physical standby on 9.2 failover fails

Hello,
I have setup physical standby database and it seems to be transferring data correctly. I tested it also be going into read only mode and querying for changes.
My problem is attempting to do a failover. I simply disconnect the primary to simulate the outtage and attempt to bring secondary by doing the following. Note that I tried both commit to switchover and activate standby.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH;
Database altered.
SQL> ALTER DATABASE ACTIVATE STANDBY DATABASE;
ALTER DATABASE ACTIVATE STANDBY DATABASE
ERROR at line 1:
ORA-00261: log 4 of thread 1 is being archived or modified
ORA-00312: online log 4 thread 1: '/u02/oradata/digidsgn/stdby_redo04a.log'
ORA-00312: online log 4 thread 1: '/u03/oradata/digidsgn/stdby_redo04b.log'
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY
2 ;
ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY
ERROR at line 1:
ORA-16139: media recovery required
The log transfer method is by LGWR...
LOG_ARCHIVE_DEST_2='SERVICE=DIGIDSGN.STBY LGWR ASYNC NOAFFIRM'
Primary database is in MAXIMIZE PERFORMANCE mode.
What am I doing wrong? I do have standby logs created, on standby the names are different from the primary ones.
Another question:
Is the switchover/failover operation suppose to create a normal control file and normal redo logs automatically?
thanks.

Well, this is gonna sound crazy, but I did a fair amount of digging and realized that I couldn't re-select my system disk as my startup disk as well (Error message said "Building boot caches on boot helper partition failed"). I was thinking the installer was trying to modify some settings on my boot volume and couldn't figure out what volume my boot volume really was.
I thought this issue and the update installer issue was related based on something in the iTunes error log looking for "Volumes/Boot OS X".
I figured if I could fix the Startup Disk issue, the other issue would be fixed as well. So I decided to poke around and figure out why I couldn't select my boot volume in the Startup Disk Preference Pane and found these instructions:
Create a new files in Terminal using this command:
*sudo nano /Library/Preferences/SystemConfiguration/com.apple.Boot.plist*
In that file, inserted the default code:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://
www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string></string>
</dict>
</plist>
Once that file was created with the proper contents, I went back to the Startup Disk Preference Pane and could select my system disk.
At that point I attempted to install the Trackpad/Magic Trackpad Updater... and it worked! HA! Then I tried iTunes... and success was found there as well.
Hope you have the same luck that I did...
Cheers,
Sapridyne

Switchover to 1 of 3 Physical Standby (oracle 10g R2)

Hi all,
Previously I already had done switchover primary to standby (only 1 Physical standby was in the configuration)
now i have some additional physical standbys (3 Physical standbys)
stby1
stby2
stby3
i want to switch to stby1 ,what needs to be done at stby2,stby3 to make them capable of identifying stby1 as their new primary.
Kindly suggest!
Best Regards,
Muhammad Shakeel Azeem

921542 wrote:
Hi all,
Previously I already had done switchover primary to standby (only 1 Physical standby was in the configuration)
now i have some additional physical standbys (3 Physical standbys)
stby1
stby2
stby3
i want to switch to stby1 ,what needs to be done at stby2,stby3 to make them capable of identifying stby1 as their new primary.
Kindly suggest!
Best Regards,
Muhammad Shakeel AzeemAzeem,
Welcome to OTN,
Once you performed switchover, You need to perform changes with some parameters from standby FAL_SERVER
Earlier this parameter points to old primary, Now after switchover you have to put service name of new primary database service.
Also Make changes with remote destinations log_archive_dest_n with correct service names.
Refer this manual to work with multiple standby databases.
http://www.oracle.com/technetwork/database/features/availability/maa10gr2multiplestandbybp-1-131937.pdf

Primary and standby init file (switchove/failover)

I have created standby database, its working fine, and logs are copying and being applied. I have successfully opened standby database in read only mode.
Now I want to perform switchover and failover, please check parameters in init file that I have added.
Primary database init file :
*.control_files='D:\oracle\product\10.2.0/oradata/primary/\control01.ctl','D:\oracle\product\10.2.0/oradata/primary/\control02.ctl','D:\oracle\product\10.2.0/oradata/primary/\control03.ctl'
*.db_name='primary'
*.db_unique_name='PRIMARY'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=primaryXDB)'
*.log_archive_dest_1='location=D:\oracle\product\10.2.0\oradata\archive'
*.log_archive_dest_state_1=ENABLE
*.log_archive_dest_state_2=ENABLE
*.log_archive_dest_2='SERVICE=standby LGWR ASYNC'
*.log_archive_format='arc_%s_%t_%r.arc'
*.fal_client='PRIMARY'
*.fal_server='STANDBY'
standby database init file :
*.control_files='D:\oracle\product\10.2.0/oradata/primary/STANDBY_CONTROL.CTL'
*.db_name='primary'
*.db_unique_name='STANDBY'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=primaryXDB)'
*.log_archive_dest_1='location=D:\oracle\product\10.2.0\oradata\archive'
*.log_archive_format='arc_%s_%t_%r.arc'
*.log_archive_dest_state_2=ENABLE
*.fal_server='PRIMARY'
*.fal_client='STANDBY'
*.standby_file_management=auto
Please let me know if I need to add/modify any parameter to perform switchover & failover operations.
Regards.

Have a look on the below links:
http://www.orafaq.com/wiki/DataGuard_implementation_for_Oracle_10gR2_
http://emrebaransel.blogspot.com/2008/08/dataguard-switchover-guide-physical09.html_

Data Guard Physical Standby Failover

I need clarification on Physical Standby Failovers. Say I have a Primary db (A) and a physical standby (B), (A) fails and (B) is now the primary, can (A) be setup to become a standby of (B)? I've read 2 different statements in Oracle 10g Data Guard Concepts and Admin
"During failovers involving a physical standby database: In all cases, after a failover, the original primary database can no longer participate in the Data Guard configuration."
vice
"After a fast-start failover occurs, the old primary database will automatically reconfigure itself as a new standby database upon reconnection to the configuration."
Much thanks.

In all cases, after a failover, the original primary database can no longer participate in the Data Guard configuration.
TRUE ! But this doesn't mean that you cannot make your failed primary a new standby database !.
You can achieve this using FLASHBACK DATABASE option:
From the documentation:
After a failover occurs, the original primary database can no longer participate in the Data Guard configuration until it is repaired and established as a standby database in the new configuration. To do this, you can use the Flashback Database feature to recover the failed primary database to a point in time before the failover occurred, and then convert it into a physical or logical standby database in the new configuration.
Read the following documents:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/role_management.htm#sthref995
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1049997
In addition to this I'd like to mention that you can achieve the same with doing an incomplete recovery instead of using FLASHBACK DATABASE.
"After a fast-start failover occurs, the old primary database will automatically reconfigure itself as a new standby database upon reconnection to the configuration."
TRUE. If you enable Fast-Start Failover:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/sofo.htm#CHDDFFEC
Cheers!

Switchover to physical standby failed

Hi gurus,
Could anyone pls help for this issue, i'm working on oracle 9i dataguard in solaris box. we succesully switchover our physical standby to primary but when tried to bring back again to physical standby it is throwing an error
SQL> alter database commit to switchover to physical standby;
alter database commit to switchover to physical standby
ERROR at line 1:
ORA-16014: log 1 sequence# 91775 not archived, no available destinations
ORA-00312: online log 1 thread 1: '/oracle/u07/oradata/odb/redo_1a.log'
ORA-00312: online log 1 thread 1: '/oracle/u08/oradata/odb/redo_1b.log'
ORA-00312: online log 1 thread 1: '/oracle/u09/oradata/odb/redo_1c.log'
Please advice
regards,
shaan

Hi,
There is already a thread which you opened Up you can reply back in that..
switchover to physical standby failed
- Pavan Kumar N

What happens at backend when we fire alter database commit to switchover to physical standby

Hi,
What exactly happens at backend when we fire alter database commit to switchover to physical standby.
how the transition happens?
Thanks

Hi,
The following will happen at the backend
1.) Notifies the primary database that a switchover is about to occur
2.) Disconnect all users from the primary database
3.) Generate a special redo record that signals the End of Redo (EOR)
4.) Converts the primary database into a standby database
5.) Once the standby database applies the final EOR record, guaranteeing that no data loss has been lost, converts the standby database into the primary database.
The new standby database (old primary) starts to receive the redo records and continues process until we switch back again. It is important to remember that both databases receive the EOR record so both databases know the next redo that will be received.
Regards,
Pradeep. V

Problem in switchover to physical standby database

Hi All,
I am doing switchover from primary to physical standby database. Physical standby is in 'managed recovery' mode using real time apply and is in mount mode. I executed alter database commit to switchover to physical standby with session shutdown command. Now i am waiting for standby mrp to exit after processing eor record, but it seems mrp was hanged.
Below is the content from standby database:
Recovery of Online Redo Log: Thread 1 Group 5 Seq 620 Reading mem 0
Mem# 0: /oracle/app/oracle/dbrac/th1-redo5a.log
Resetting standby activation ID 749049115 (0x2ca5951b)
Media Recovery End-Of-Redo indicator encountered
Media Recovery Continuing
Media Recovery Waiting for thread 1 sequence 621
Archived Log entry 14 added for thread 1 sequence 620 ID 0x2ca5951b dest 1:
Need some help to resolve.
Thanks
Sandy.

Hello;
After after you issue ( successfully ) a :
alter database commit to switchover to physical standby with session shutdownYou need to :
Shutdown the former primary and mount as a standby databaseCheck out my step by step :
http://www.visi.com/~mseberg/data_guard/Data_Guard_switchover.html
Read everything ( all the steps ) before you proceed.
Best Regards
mseberg

Physical Standby Online Redo log files,

Hi,
I'm trying to create a physical standby database (10.2.0.3). I'm a little confused about the requirement for online redo logs on the standby.
in my standby alert log I get the following when I issue:
SQL> alter database recover managed standby database disconnect from session
"ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/appl/oradata/prod/prod_1_redo_01_02.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3"
/appl/oradata/prod/prod_1_redo_01_02.log is the path to the location of the online redo logs on the production system. This file does not exist on the standby filesystem so the error is correct.
I assume that it gets this information from the standby control file I created on the production system and copied over to the standby.
Do I need to copy the online redo logs from the primary over to the standby site or do I need to create online redo logs on the standby?
Does the standby need to have redo log files?
I'm not talking about 'standby log files' of the type created using 'alter database add standby log file'. I've not got that far yet.
I just need to establish if a physical standby requires online redo log files?
Thanks in advance,
user234564

I wanted to update this thread since I've been dealing with the exact same errors. The basic question is: "does a physical standby need the online redo logs?"
Answer: Not really, until one wants to switchover or failover (and become a primary database). Furthermore, whenever the MRP process is started, Oracle prepares for a possible switchover/failover by "clearing" the online redo logs (MetaLink note# 352879.1). It is not a big deal, since Oracle will build the actual redo files when the "alter database open resetlogs" is accomplished during a "role transition."
In our situation, we have decided to use our standby for nightly exports. We stop MRP, open the database read-only, then restart MRP. We built these standby DBs with RMAN. The RMAN duplicate process will not build the online redo log files until the database is opened for read/write (with resetlogs). However, we haven't had a need for read/write (i.e. a switchover).
Thus, every morning we have been getting the same errors that "user234564" posted above. At first the errors seemed scary, then we realized they were just a nusiance. In order to clean things up, all I did was just "cp" our stanby redo logs (SRL) into our online redo directories ensuring the names matched what was in v$logfile. When I restarted MRP, the alert log clearly showed Oracle clearing these "newly found" online redo logs.

Switchover/Failover to physical standby

Similar Messages

Maybe you are looking for