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.

Similar Messages

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

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

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

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

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!

Problems while creating a physical Standby

Hi,
I am trying to setup a physical standby database with oracle 10g.
I configured a specific log archive destination:
LOG_ARCHIVE_DEST_3 = 'SERVICE=ORAMPSEC REOPEN=60 MAX_FAILURE=3 LGWR SYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=ORAMPSEC'
The service is reachable via network.
To establish the standby database I copied all datafiles from the primary database using scp. I also created a standby controlfile and a modified pfile. In addition I added a standby redo logfile which has the same size as the online redo log files on the primary database.
After starting the standby database in open read only mode I receive the following error message:
Database mounted.
ORA-16004: backup database requires recovery
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oradata/ORAMPPRD/data/system01.dbf'
I tried to recover using "recover standby database" I receive the following message:
ORA-00279: change 884348 generated at 07/18/2006 17:08:07 needed for thread 1
ORA-00289: suggestion : /oradata/ORAMPPRD/archive/1_30_595767954.dbf
ORA-00280: change 884348 for thread 1 is in sequence #30
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Although I transmitted all archived log files from the primary database the archived log file mentioned above is not available. After hitting RETURN I get this message:
ORA-00308: cannot open archived log
'/oradata/ORAMPPRD/archive/1_30_595767954.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oradata/ORAMPPRD/data/system01.dbf'
Here is a listing of all archived logfiles from the primary database:
bash-3.00$ ls -latr
total 494144
drwxr-xr-x 6 oracle oinstall 512 Jul 14 11:03 ..
-rw-r----- 1 oracle oinstall 20732928 Jul 17 11:47 1_6_595767954.dbf
-rw-r----- 1 oracle oinstall 86013440 Jul 17 13:56 1_7_595767954.dbf
-rw-r----- 1 oracle oinstall 214016 Jul 17 13:57 1_8_595767954.dbf
-rw-r----- 1 oracle oinstall 1986560 Jul 17 14:10 1_9_595767954.dbf
-rw-r----- 1 oracle oinstall 150016 Jul 17 14:10 1_10_595767954.dbf
-rw-r----- 1 oracle oinstall 504320 Jul 17 14:17 1_11_595767954.dbf
-rw-r----- 1 oracle oinstall 1807872 Jul 17 14:22 1_12_595767954.dbf
-rw-r----- 1 oracle oinstall 589824 Jul 17 14:25 1_13_595767954.dbf
-rw-r----- 1 oracle oinstall 1190912 Jul 17 14:37 1_14_595767954.dbf
-rw-r----- 1 oracle oinstall 584704 Jul 17 14:42 1_15_595767954.dbf
-rw-r----- 1 oracle oinstall 80896 Jul 17 14:45 1_16_595767954.dbf
-rw-r----- 1 oracle oinstall 6050816 Jul 17 15:08 1_17_595767954.dbf
-rw-r----- 1 oracle oinstall 4238848 Jul 17 16:04 1_18_595767954.dbf
-rw-r----- 1 oracle oinstall 4920832 Jul 17 17:21 1_19_595767954.dbf
-rw-r----- 1 oracle oinstall 1520128 Jul 17 17:30 1_20_595767954.dbf
-rw-r----- 1 oracle oinstall 360960 Jul 17 17:35 1_21_595767954.dbf
-rw-r----- 1 oracle oinstall 89186304 Jul 18 10:52
1_22_595767954.dbf
-rw-r----- 1 oracle oinstall 16216576 Jul 18 14:18
1_23_595767954.dbf
-rw-r----- 1 oracle oinstall 12288 Jul 18 14:18 1_24_595767954.dbf
-rw-r--r-- 1 oracle oinstall 2073 Jul 18 14:26 sqlnet.log
-rw-r----- 1 oracle oinstall 14387200 Jul 18 16:56
1_25_595767954.dbf
-rw-r----- 1 oracle oinstall 116736 Jul 18 16:58 1_26_595767954.dbf
-rw-r----- 1 oracle oinstall 1536000 Jul 18 17:04 1_27_595767954.dbf
-rw-r----- 1 oracle oinstall 156672 Jul 18 17:05 1_28_595767954.dbf
drwxr-xr-x 2 oracle oinstall 1024 Jul 18 17:08 .
-rw-r----- 1 oracle oinstall 65536 Jul 18 17:08 1_29_595767954.dbf
Nothing known about the *30*dbf file.
Although there still seems to be something wrong, the archived log file transmission seems to work since there is no error reported on the log archive destination:
SQL> select status, error from v$archive_dest where dest_id = 3;
STATUS ERROR
VALID
And after I manually force a log switch I see that archived redo logs were applied on the standby database:
select sequence#, applied from v$archived_log order by sequence#;
SEQUENCE# APPLIED
27 YES
28 NO
28 YES
29 NO
29 YES
Unfortunately because of the recovering problem I cannot open the database to see if the changes were applied. So my first question is, how can I get the standby database completely recovered ??
In addition to this I was expecting that the changes to the standby database were made immediately since I choosed LGWR sync but I have to manually force the logfile switch. As I already mentioned a standby redo log file is available as well.
Thanks for your help,
Philipp.

Hi,
since it does not seem to work with just copying the datafiles I switched to RMAN. I created a full database backup from Enterprise Manager. Similiar to http://dizwell.com/main/content/view/81/122/1/1/ I tried to duplicate the database to the standby instance (running on a different server). But unfortunately I receive error messages that the files, previously created, cannot be found:
channel d1: starting datafile backupset restore channel d1: specifying datafile(s) to restore from backup set restoring datafile 00001 to /oradata/ORAMPPRD/data/1.dbf restoring datafile 00002 to /oradata/ORAMPPRD/data/2.dbf restoring datafile 00003 to /oradata/ORAMPPRD/data/3.dbf restoring datafile 00004 to /oradata/ORAMPPRD/data/4.dbf channel d1: reading from backup piece /opt/oracle/ora10/product/10.2.0.1.0/dbs/0bhoiq60_1_1
ORA-19870: error reading backup
piece /opt/oracle/ora10/product/10.2.0.1.0/dbs/0bhoiq60_1_1
ORA-19505: failed to identify file
"/opt/oracle/ora10/product/10.2.0.1.0/dbs/0bhoiq60_1_1"
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory Additional information: 3 failover to previous backup
But when I crosscheck my backup inside RMAN it clearly shows the backup files:
RMAN> crosscheck backup;
backup piece
handle=/opt/oracle/ora10/product/10.2.0.1.0/dbs/0bhoiq60_1_1 recid=7
stamp=596207811
crosschecked backup piece: found to be 'AVAILABLE'
I already checked the file permissions, everybody on the system is able to access this file.
Do you know what is going wrong here ??
Cheers,
Philipp.

Problem in identifying control file when creating physical standby

hi there,
(database version: 10.2.0.4
plateform linux)
I'm using the command as below to create physical standby database from backup:
rman target / auxiliary sys/tiger@paceview
Recovery Manager: Release 10.2.0.4.0 - Production on Tue Sep 4 18:05:53 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: PACEVIEW (DBID=2092349485)
connected to auxiliary database: PACEVIEW (not mounted)
run {
allocate auxiliary channel c1 device type DISK;
set until sequence 38;
duplicate target database for standby dorecover nofilenamecheck;
released channel: ORA_DISK_1
allocated channel: c1
channel c1: sid=35 devtype=DISK
allocated channel: c2
channel c2: sid=36 devtype=DISK
executing command: SET until clause
Starting Duplicate Db at 04-SEP-12
contents of Memory Script:
   set until scn 138180211934;
   restore clone standby controlfile;
   sql clone 'alter database mount standby database';
executing Memory Script
executing command: SET until clause
Starting restore at 04-SEP-12
channel c1: restoring control file
ORA-19625: error identifying file /backup/rman/paceview/DEL1_standby.ctl
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-19600: input file is control file (/backup/rman/paceview/DEL1_standby.ctl)
ORA-19601: output file is control file (/PGHProdDB/oradata/paceview/control1.ctl)
failover to previous backup
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/04/2012 18:01:44
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restorei have already tried crosscheck but still giving same error
thanks

Hello;
So this is what I would do :
Backup Primary ( change to your directory as need )
RMAN RUN {
allocate channel d1 type disk;
backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
sql 'alter system archive log current';
backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
release channel d1;
}Move the backup and duplicate like this :
rman target sys/password@PRIMARY auxiliary /
RMAN> run {
allocate channel C1 device type disk;
allocate auxiliary channel C2 device type disk;
duplicate target database for standby nofilenamecheck;
}For complete details of this method see :
http://www.visi.com/~mseberg/duprman2.html
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.

Physical standby database in RAC system

Hi EXperts,
We have a 4 nodes 11.2 cluster system. i will set a data guard as a disaster recovery mothods.
As a physical standby database set, does we need to configure same nodes (4 nodes) in other city as primary database cluster system?
Can we set physical standby database is in 2 nodes cluster system and primary database is in 4 nodes cluster system?
Thanks explaining!
Jin

Can we set physical standby database is in 2 nodes cluster system and primary database is in 4 nodes cluster system?Yes. You can setup 2 node RAC as physical standby and also with different memory parameters. But, the only issue is when DB failover from primary to standby, the applications connect to 2 node RAC in place of 4 node RAC and may be overloaded.

Physical Standby database Vs. Logical Standby database

I have few questions regarding capability of Logical Standby Database against Physical Standby database.
1. How efficient is Logical Standby database in terms of Physical Standby Database?? How both differ from each other and can I use Logical Standby Database for disaster Recovery?? Can It be use for recovering the failed Primary Instance?? If yes how efficient and reliable it is??
2. What are the known bugs and roadblocks for logical standby database on Oracle 10.2.0.1 on Soalris X86-64?
3.As logical standby database not going to replicate each and every schema of Primary database?? how is the change management effects to the logical standby from primary?? I mean there are some parameters and job that we create on primary how can it be transferred over to the logical standby??

1. How efficient is Logical Standby database in terms
of Physical Standby Database?? How both differ from
each other and can I use Logical Standby Database for
disaster Recovery?? Can It be use for recovering the
failed Primary Instance?? If yes how efficient and
reliable it is??I'm not sure what sort of "efficiency" you're talking about here...
Physical standby is just the old, tried and true application of archived logs to recover a database. Very solid, very old school.
Logical standby, on the other hand, is parsing the redo log, extracting logical change records, and applying them to the standby database. This obviously takes a bit more processing effort, it's newer technology, it doesn't have quite the level of support that physical standby does (i.e. certain data types are excluded), etc. You certainly can use it for failover, but it isn't quite as robust as a physical standby. Of course, this is getting better and better all the time and is definitely a focus of Oracle's development efforts.
On the other hand, logical standby systems can do things other than act as a warm standby. They can be open serving reports, for example. You can create additional structures (i.e. new materialized views) to support reporting. A physical standby is pretty much always going to be in managed recovery mode, so it cannot be queried.
2. What are the known bugs and roadblocks for logical
standby database on Oracle 10.2.0.1 on Soalris
X86-64?a) You'll want to do a Metalink search
b) If you're talking about a high-availability solution, why are you looking at a base release of the database? Why wouldn't you apply the latest patchset?
3.As logical standby database not going to replicate
each and every schema of Primary database?? how is
the change management effects to the logical standby
from primary?? I mean there are some parameters and
job that we create on primary how can it be
transferred over to the logical standby??I'm not sure I understand... Changes made to the primary generate redo. Oracle parses that redo, generates a LCR, and sends that to the standby database where that change record gets applied.
Justin

Online redo logs on a physical standby?

A question on REDO logs on physical standby databases. (10.2.0.4 db on Windows 32bit)
My PRIMARY has 3 ONLINE REDO groups, 2 members each, in ..ORADATA\LOCP10G
My PHYSICAL STANDBY has 4 STANDBY REDO groups, 2 members each, in ..ORADATA\SBY10G
I have shipping occurring from the primary in LGWR, ASYNC mode - max availablility
However I notice the STANDBY also has ONLINE REDO logs, same as the PRIMARY, in the ..ORADATA\SBY10G folder
According to the 10g Dataguard docs, section 2.5.1:
"Physical standby databases do not use an online redo log, because physical standby databases are not opened for read/write I/O."
I have tried to drop these on the STANDBY when not in apply mode, but I get the following:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
Database altered.
SQL> ALTER DATABASE DROP LOGFILE GROUP 3;
ALTER DATABASE DROP LOGFILE GROUP 3
ERROR at line 1:
ORA-01275: Operation DROP LOGFILE is not allowed if standby file management is
automatic.
I also deleted them while the STANDBY instance was idle, but it recreated them when moved to MOUNT mode.
So my question is why is my PHYSICAL recreating and using these, if the docs say the shouldn't?
I saw the same error mentioned here: prob. with DataGuard
Is this a case of the STANDBY needing at least a notion of where the REDO logs will need to be should a failover occur, and if the files are already there, the standby database CONTROLFILE will hold onto them, as they are not doing any harm anyway?
Or, is this a prooduct of having management=AUTOMATIC - i.e. the database will create these 'automatically'
Ta
bt

According to the 10g Dataguard docs, section 2.5.1:
"Physical standby databases do not use an online redo log, because physical standby databases are not opened for read/write I/O."yes, those are used when database is open.
You should not perform any changes in Standby. Even if those exist online redo log files, whats the difficulty you have seen?
These will be used whenever you performed switchover/failover. So nothing to worry on this.
Is this a case of the STANDBY needing at least a notion of where the REDO logs will need to be should a failover occur, and if the files are already there, the standby database CONTROLFILE will hold onto them, as they are not doing any harm anyway?Then oracle functionality itself harm if you think in that way. When they not used in open then what the harm with that?
Standby_File_management --> for example if you add any datafile, those information will be in archives/redos once they applied on standby those will be added automatically when it is set to AUTO if its manual, then it creates a unnamed file in $ORACLE_HOME/dbs location later you have to rename that file and recovery need to perform .
check this http://docs.oracle.com/cd/B14117_01/server.101/b10755/initparams206.htm
HTH.

Oracle 10g physical standby error

Hi all,
We been frequently getting this error on our standby DB and not sure if it's network related or a possible configuration tuning.
RFS[425]: Assigned to RFS process 3640
RFS[425]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[425]: No standby redo logfiles created
Mon Nov 23 09:47:28 2009
Fetching gap sequence in thread 1, gap sequence 35418-35418
Mon Nov 23 09:48:02 2009
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 35418-35418
DBID 3292763437 branch 615642223
FAL[client]: All defined FAL servers have been attempted.
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
Mon Nov 23 09:48:17 2009
RFS[384]: No standby redo logfiles created
Mon Nov 23 09:48:21 2009
RFS[425]: Possible network disconnect with primary database
Closing latent archivelog for thread 1 sequence 35419
EOF located at block 1201 low SCN 0:-1055223653 next SCN 0:-1055223015
Latent archivelog 'E:\ORACLE\ARCH\xxxxx\LOG_615642223_1_35419.ARC'
If you wish to failover to this standby database, you should use the
following command to manually register the archivelog for recovery:
ALTER DATABASE REGISTER LOGFILE 'E:\ORACLE\ARCH\xxxxx\LOG_xxx615642223_1_35419.ARC';
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[426]: Assigned to RFS process 3200
RFS[426]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[426]: No standby redo logfiles created
Any ideas?
thx

I've inherited this DB and never really looked at the settings.
The error I see in the primary DB is
FAL[server]: Fail to queue the whole FAL gap
Protection level on primary is
SQL> SELECT PROTECTION_MODE, PROTECTION_LEVEL FROM V$DATABASE;
PROTECTION_MODE PROTECTION_LEVEL
MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE
Edited by: jrmtl on Nov 23, 2009 7:32 AM

Dataguard (10.2.0.5) - physical standby (async, real time apply)

Hi Guys,
Just wondering.
For eg, I have a Production Database and a physical standby DB.
Only the physical standby DB has flash back on.
For eg, one day if there's a need for me to restore the production DB from tape (point in time recovery, so need to resetlogs).
Do i need to rebuild the physical standby DB? (from the backup of restored db)
Or can i make use of flash back? If i make use of flash back, i will have to re-create the control file right?
thanks

Hello;
Within Data Guard can use Flashback for the following :
On the Standby to recover data because of a delay in the apply process.
On the Standby ( Physical ) to open the database in snapshot mode.
On the Primary and Standby to flash the database back in time (if Standby then Primary must flashback too)
On the Primary to recover the database after a failover.If I understand you question correctly you are talking "Incomplete recovery" on the Primary with no Flashback there. So the answer is No, Flashback on the Standby cannot help.
You can correct this by setting up flashback on the Primary.
Best Regards
mseberg

Failover to Physical Standby

Similar Messages

Maybe you are looking for