Primary database is RAC and Physical standby is single instance

Hello All,
I am using Oracle RAC 11.2.0.3 as primary database, we are going to start using Oracle data guard.
So I am designing my infrastructure and planing to use Oracle 11.2.0.3 Single instance as my physical stand by database.
My question is it feasible to have my standby database as single instance while the primary is RAC?
is it feasible to build my Oracle single instance standby database from the RMAN backup of the RAC primary database?
Is there any restrictions (or any points to be taken into consideration) since my primary database is RAC while the physical standby is Oracle single instance?
in the below link
[http://docs.oracle.com/cd/B28359_01/server.111/b28294/concepts.htm#i1039416]
it was mentioned that primary can be RAC or single and same for standby, but my question is it feasible to have primary as RAC while standby as single instance? or it should be like each others?
The primary database can be either a single-instance Oracle database or an Oracle Real Application Clusters (RAC) database.
Similar to a primary database, a standby database can be either a single-instance Oracle database or an Oracle RAC database.Regards,

My question is it feasible to have my standby database as single instance while the primary is RAC?Yes...quite a common setup.
is it feasible to build my Oracle single instance standby database from the RMAN backup of the RAC primary database?Yes.
Is there any restrictions (or any points to be taken into consideration) since my primary database is RAC while the physical standby is Oracle single instance?No show stoppers.

Similar Messages

Data guard synchronization after link down b/w primary and physical standby

Hi All,
I have configured data guard on oracle 11gr2 db. Normally switchover between my primary and physical standby happens smoothly and the Apply lag would be zero. Recently We had to test a scenario when the network link between Primary and Physical standby is completely down and Physical standby is isolated completely for more than half an hour.
When we brought up the link every thing worked smoothly but apply lag started increasing from 0 to around 3 hrs. And then it started reducing to 0. Currently Apply lag and transport lag shows 0.
But is this normal behaviour of oracle data guard that when the link between primary and physical standby is completely down, It requires 3-4 hrs for resynchronization ??? Even when during isolation, there were very few transactions happend on primary database ??
Are there any documents available for this scenario??
Thanks

Hi, after the link is up, if there were some transactions and produced archive logs it's normal to take some time for resync. To check if 3-4 hours is normal or not, you can repeat the scenario and this time check
- how many archivelogs does primary produce in this period.
- after the link is up, does archivelog transfer immediately starts from primary to standby? Is primary able to send these archivelogs parallel?
- Is there anything wrong with the apply process?
check primary & standby alert log files, and run this query on standby to check the transport and apply processes:
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
regards

Time zone difference between primary and physical standby

Dear Team,
We have Primary database server (with EST Time zone) and physical standby (with PST time zone), in case of switch over/fail over to physical standby
what are the major impacts.
Is it mandatory to be in time sync?
Thanks in advance
Aj

CURRENT_TIMESTAMP
04-FEB-10 10.22.20.444692 AM +05:30
( above is same on primary and standby)
SQL> select systimestamp from dual;
SYSTIMESTAMP
03-FEB-10 08.52.46.934125 PM -08:00
(above is 3hr diff from primary and standby)It is 13hrs difference
One is around Indian subcontinent and other should be in US western region ?
Systimestamp is the timestamp of the OS of the server and hence the difference and the sysdate value will be from systimestamp and if the applications uses SYSDATE then there can be an issue...

ASM on primary and physical standby on normal filesystem

Hi
I have seen he white paper by oracle on migrating a database to ASM with minimal downtime using ASM for a physical standby my requirement is reverse.
I need to have a ASM for a primary database but no ASM for standby database.
How do we set the parameter db_file_name_convert
regards
Hrishy

db_file_name_convert covers the folder path for the files. I don't think, there will be issue.
If we use rman, it will use the folder path per db_file_name_convert and retain the old file names. OMF naming will apply for the new files.
Ashok

RAC & DataGuard (Physical Standby)

Hello all,
I'm trying to get a high level overview of how RAC & DataGuard would behave in the following configuration. I've written down my understanding of how things would work. Please correct me if I'm wrong.
1) 2 node RAC (Primary Database) with a single instance physical standby.
a) Same standby related init.ora parameters would have to configured on both primary rac nodes.
b) The redo apply service at the standby would merge the redo from the 2 threads from the primary and apply it to the standby to keep it in sync.
c) During switch over only one primary RAC instance should be up besides the standby instance.
d) During switch back again only one primary RAC instance should be up besides the standby instance.
e) During failover ofcourse both primary instances would be down which warrants the fail over.
2) 2 node RAC (Primary) with a 2 node physical standby
This where it gets complex and I'm not really sure how a,b,c,d,e would be in this scenario. Appreciate if you could shed some light on this and list what
a,b,c,d,e would look like in this scenario.
I'm assuming that only one instance in the standby RAC should be up when the standby is in RAC configuration for the redo apply to work.
Also, if there is a white paper that details step by step procedure for setting up the above 2 scenarios, please let me know. So far I was able to find only the MAA white paper but that was not very helpful. If you can prescribe a good book for RAC & DataGuard that would be great too..
Thanks for your help

>
1) 2 node RAC (Primary Database) with a single instance physical standby.
a) Same standby related init.ora parameters would have to configured on both primary rac nodes.Usually rac nodes share their spfile on a shared diskvolume or through ASM. So they have identical DG parameter anyway
b) The redo apply service at the standby would merge the redo from the 2 threads from the primary and apply it to the standby to keep it in sync.Correct
c) During switch over only one primary RAC instance should be up besides the standby instance.
Sounds logical to me
Edit: In fact during normal operation both RAC nodes are up, so during switchover they are both active too
It is the configuration that matters. As soon as the standby is becoming primary, it might be that it talks only to one RAC node for its log-apply files
d) During switch back again only one primary RAC instance should be up besides the standby instance.That single was the only one running in step c.
e) During failover ofcourse both primary instances would be down which warrants the fail over.Correct. Keep in mind that during a failover the RAC config would be deconfigured from the DG setup and has to be added back again as standby.
You might have to take a look at: http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimarySingleInstancePhysicalStandby.pdf
>
2) 2 node RAC (Primary) with a 2 node physical standby
This where it gets complex and I'm not really sure how a,b,c,d,e would be in this scenario. Appreciate if you could shed some light on this and list what
a,b,c,d,e would look like in this scenario.
I'm assuming that only one instance in the standby RAC should be up when the standby is in RAC configuration for the redo apply to work.
No. RAC primary to RAC Standby would mean both nodes are up on both side. PrimNode1 send its redo logs to StandbyNode1 and the same for PrimNode2 and StandbyNode2
Have a look here: http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimaryRACPhysicalStandby.pdf
HTH,
FJFranken
My Blog: http://managingoracle.blogspot.com
Edited by: fjfranken on 16-jul-2010 1:13

Logical and Physical Standby on same Node

Is it possible to have a logical and physical standby database for a primary database on the same node (i.e. primary on NodeA, logical and physical database of primary on NodeB)?
Will there be any conflicts with data guard broker with this configuration or any problems I may encounter?

From a technical point of view this is possible. Your standby node should be powerful enough to handle 2 instances. For even higher availability 3 dedicated nodes would be better. When Node B is down, both physical and logical standby are also down.
Werner

10g Primary database work with a 11g Standby database

Can a 10g Primary database work with a 11g Standby database?
The existing database is Oracle 10g and I don't want to upgrade it. But I really need the Real-time Query feature of 11g Physical Standby Database.
Can they work together?

Hi,
do you have any proof?
I never find any proof in Oracle Docs.Kindly refer to doc's and check things it states Primary and Standby Servers Versions must be same - similar to that you can find very much clear. That is more than enough for proof else Test it you will find your self...;-).
- Pavan Kumar N
Oracle 9i/10g - OCP
http://oracleinternals.blogspot.com/

Upgrading the primary and physical standby database

Solaris 9
oracle 9i (9.2.0.8)
upgrade to 10g (10.2.0.3)
Hi,
I would like to know how to upgrade database in dataguard envronment.(primary and remote physical standby database)
Is rolling upgrade possible in this case?
Or any steps or Document is appreciated.
Thanks.
Message was edited by:
user539835

Read this Metalink Note:407040.1

Primary and Physical Standby databases hanging on sqlplus shell command...

I am primarily a java developer that has had the task of oracle dba thrust upon me due to circumstances that are beyond my control. In the QA lab we have two oracle 10 g release 1 instances running. They set up in a dataguard configuration: one is the primary and the other is in a physical standby.
Last week I noticed that the disk space on the primary database was at 100%. After some investigation I discovered that a good deal of the files taking up space on the box were log files and the best solution that I could think of would be to delete all old archive files. So I deleted the old archive files that were at least two weeks old using RMAN.
During this week the database started to shutdown automatically. The QA associate restarted the database twice using the ‘STARTUP’ command from sqlplus. Additionally, the standby database began to have issues: when login in to sqlplus the application would just hang: no ‘SQL” prompt or anything. Finally today the primary database has also begun to hang in a similar manner.
I have looked at many of the trace files and alert logs but haven’t been able to really discern what the real problem is with the database and the proper rectification for the database. Does anyone have a clue into what is going on? If someone could even point me in the right direction it would be greatly appreciated.

Guessing that your flash recovery area is full, archiving is stopped so the instance appears to hang.
Do you see messages like so in the alert log:
You have following choices to free up space from flash recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
   then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
   BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
   reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
   system command was used to delete files, then use RMAN CROSSCHECK and
   DELETE EXPIRED commands.
************************************************************************

Configuring both logical and physical standby databases.

Hi,
I am trying to set up one primary and two standby databases which are physical and logical. together. What I am wondering is if i tis posiible to set both log_archive_dest_n parameters in init.ora of primary db to 'LGWR ASYNC'.. I tried to do that but I noticed that while redo data goes the first remote log destination including LGWR statement properly but for the second it does not.
So my assumption is only one remote archive dest. can be set for the LGWR process. Is ıt right?
Regards
ALPER ONEY
email:[email protected]

Hi,
when I set remote archive dest _n parameter for logical standby database to the value like 'LGWR AYSNC' and for the phy. standby to 'ARCH', it is ok. But if I change both parameters to 'LGWR'. I can see that only one destination receives the redo data and this destination is also the first destination configured for receiving redodata . I am just wondering that LGWR process is able to serve two or more to destinations at the same time. If it is ok, I am wrong and I better to try harder to solve the problem. I read the Dataguard document for 10GR' and the example for the case I created (two standby databases),, it uses ARCH process to send redo data and so everything is ok in that example.
P.S I also configured standbys for real time apply.
Waiting for your comments.
Regards.
ALPER ONEY

11gR2 dataguard using a primary 2 node RAC and a single standby

Hi,
I need to implement dataguard between 11gR2 RAC db to a single standby. How do I proceed?
Secondly, I need to timely apply the archive log i.e I need the dataguard to be in SYNC mode only in the night and the standby in read only
mode rest of the times. Can I achieve this using dataguard broker? If yes, can you please provide me the steps?
regards,
Ram

Doing that would require jobs again.
In your example:
9 am:
alter database recover managed standby database cancel;
-- here you can actually specify anything greater 780 because of the cancel at 10 pm; this is just to make sure the archive logs are being shipped.
alter database recover managed standby database delay=780 disconnect from session;
-- and, if your requriement is still to have the standby open read only
alter database open read only;
10 pm:
shutdown immediate;
startup nomount;
alter database mount standby database;
alter database recover managed standby database cancel;
alter database recover managed standby database using current logfile disconnect from session;
with that setup:
- your standby stops recovering at 9am
- the archive logs of the primary will still be shipped to your standby side for any emergency
- you'll have an open read only standby from 9am to 10pm
- the archive logs will be real time applied from 10pm to 9am
Note that this is just theory at the moment, I don't have a test set up like this. But it should give you an idea of what's possible and in what way you can accomplish your needs.

Primary RAC with physical standby

Hi all,
i have production setup as below
2 node 10gR2 RAC on win2K3 datafiles on ASM
Oracle Standard edition
On the standby site it will be a manual standby (since SE) .
Biz doesnt want the archives to be on local NTFS partition, hence the archives are on ASM. To resfresh the standby i need to transfer the archives through RMAN (catalog database is used) but facing issues when i take archive backup and put it on standby (error says that the files are already on storage) . So i am unable to refresh .
i guess it should be done through some scripts .... but how to register archives on the standby site.
Xml interface through catxdb was also tried(where we can ftp files from asm) but it takes only one file at a time so there will be manual intervention and not effective strategy
one more question: can i mount a shared drive (archives on this location) on primary RAC and same to be mounted on standby. If this is possible then i just need to shutdown the standby and give path of archives in asm and recovery can be done ?
pls share your feedback.....
thanks
[email protected]

So what I would do is this :
On the Primary :
alter system set log_archive_dest_state_2=defer;
Then stop recovery on the Standby and shutdown the database.
Startup mount and start recovery again and run you query again on that sequence.
If it finally clears enable the primary again.
alter system set log_archive_dest_state_2=enable;
If not try to register it yourself.
By chance does this show its waiting for a gap
select process, status, sequence#, block# from v$managed_standby;Best Regards
mseberg
Edited by: mseberg on Aug 23, 2011 8:38 AM

Backing up primary and physical standby

We have a DG setup with a single instance primary node and a physical standby db. They both use their own FRA's and their own disks. Nothing is shared. Also the datafiles use OMF on both the db's. My questions are
1. Can i register the primary with the rman catalog and still backup the standby?
2. Should i backup the archive logs on primary? If so what rman settings should i use on both for the archive logs?
3. We wanted to back up both the dbs as it will be faster to restore since we wont have to convert filenames (cause of OMF) when we have to resotore backup taken on primary to standby or vice versa.
Any advise related to this scenario is highly appreciated.
Thanks.

Hi All,
you should have same rman format setting and log_archive_format on primary and standby database >to avoide any confusion at the time of restore. if you have different log_archive_format on standby then >primary, you might have to rename your archivelogs from standby to log_archive_format on primary.It is not required to have same log_archive_format for primary and standby database.
The database can be restored and recovered successfully even if the format is different.
Primary database
============
SYS @ oraprim> show parameter log_archive_format
NAME TYPE VALUE
log_archive_format string ARC%S_%R.%T
Standby database
=============
SYS @ orastdby> show parameter log_archive_format
NAME TYPE VALUE
log_archive_format string ARC_STDBY%S_%R.%T
Standby database
=============
C:\> set ORACLE_SID=orastdby
C:\>rman target / catalog recat/recat@recat
RMAN> backup archivelog all delete input;
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=98 recid=15 stamp=631239054
input archive log thread=1 sequence=99 recid=16 stamp=631239055
input archive log thread=1 sequence=100 recid=17 stamp=631239055
input archive log thread=1 sequence=101 recid=19 stamp=631239111
input archive log thread=1 sequence=102 recid=18 stamp=631239110
channel ORA_DISK_1: starting piece 1 at 22-AUG-07
channel ORA_DISK_1: finished piece 1 at 22-AUG-07
piece handle=C:\FLASH_RECOVERY_AREA\ORASTDBY\BACKUPSET\2007_08_22\O1_MF_ANNNN_TAG20070822T001717_3DQG6HGS_.BKP
tag=TAG20070822T001717 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
channel ORA_DISK_1: deleting archive log(s)
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00098_0630878042.001 recid=15 stamp=631239054
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00099_0630878042.001 recid=16 stamp=631239055
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00100_0630878042.001 recid=17 stamp=631239055
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00101_0630878042.001 recid=19 stamp=631239111
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00102_0630878042.001 recid=18 stamp=631239110
Finished backup at 22-AUG-07
RMAN>
Primary Database
=============
-- deleted users datafile and did complete recovery
C:\>set ORACLE_SID=oraprim
C:\>rman target / catalog recat/recat@recat
RMAN> run{
2> startup mount;
3> restore database;
4> recover database;
5> }
Oracle instance started
database mounted
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=98
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=99
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=100
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=101
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=102
channel ORA_DISK_1: reading from backup piece C:\FLASH_RECOVERY_AREA\ORASTDBY\BACKUPSET\2007_08_22\O1_MF_ANNNN_TAG20070822T001717_3DQG6HGS_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\FLASH_RECOVERY_AREA\ORASTDBY\BACKUPSET\2007_08_22\O1_MF_ANNNN_TAG20070822T001717_3DQG6HGS_.BKP tag=TAG20070822T001717
channel ORA_DISK_1: restore complete, elapsed time: 00:00:04
archive log filename=C:\ORADATA\ORA10GR2DB1\ARCH2\ARC00098_0630878042.001 thread=1 sequence=98
archive log filename=C:\ORADATA\ORA10GR2DB1\ARCH2\ARC00099_0630878042.001 thread=1 sequence=99
archive log filename=C:\ORADATA\ORA10GR2DB1\ARCH2\ARC00100_0630878042.001 thread=1 sequence=100
media recovery complete, elapsed time: 00:00:07
Finished recover at 22-AUG-07
RMAN>
Regards,
Vaibhav

ARCHIVELOG deletion on primary and physical standby

Hi,
We have a primary and a physical standby database running Oracle 11.1.0.7.0 software on Red Hat Enterprise Linux x-64 bit OS. I will be using backup software
to only backup the primary database and do not have the backup software for the standby server and database.
We need to backup archived redo log files from primary site and delete the ones which are more than one month old. These archived redo log files will be applied from primary to standby database as and when the log switch occurs.
Can anybody please let me know if the following steps can be used:
Details are:
primary database name - sun (machine name is node1)
standby database name - drsun (machine name is node2)
On node1 as oracle user:
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_sun.sh
#!/bin/sh
ORACLE_SID=sun; export ORACLE_SID
ORACLE_HOME=/u01/app/oracle/product/11.1.0/db_1; export ORACLE_HOME
PATH=$ORACLE_HOME/bin; export PATH
$ORACLE_HOME/bin/rman target sys/oracle@sun nocatalog log=/export/home/oracle/rman/log/cleanup_rman_arch_sun.log
@/export/home/oracle/rman/scripts/cleanup_rman_arch_sun.rcv
exit
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_sun.rcv
allocate channel for delete type disk;
crosscheck archivelog all;
sql "alter system switch logfile";
delete noprompt expired archivelog all;
change archivelog until time 'SYSDATE-1' delete;
release channel;
$ crontab -l
# Delete the archived redo log files at 11:00 PM on the first day of every month
00 23 1 * * /export/home/oracle/rman/scripts/cleanup_rman_arch_sun.sh
On node2 as oracle user:
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.sh
#!/bin/sh
ORACLE_SID=drsun; export ORACLE_SID
ORACLE_HOME=/u01/app/oracle/product/11.1.0/db_1; export ORACLE_HOME
PATH=$ORACLE_HOME/bin; export PATH
$ORACLE_HOME/bin/rman target sys/oracle@drsun nocatalog log=/export/home/oracle/rman/log/cleanup_rman_arch_drsun.log
@/export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.rcv
exit
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.rcv
allocate channel for delete type disk;
crosscheck archivelog all;
sql "alter system switch logfile";
delete noprompt expired archivelog all;
change archivelog until time 'SYSDATE-1' delete;
release channel;
$ crontab -l
# Delete the archived redo log files at 11:00 PM on the first day of every month
00 23 1 * * /export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.sh
Regards

Hello;
Welcome to the forums. ( By physical Standby I assume Data Guard )
The short answer is it should work. I noticed this :
/cleanup_rman_arch_drsun.rcv
crosscheck archivelog all;
sql "alter system switch logfile";
delete noprompt expired archivelog all;
change archivelog until time 'SYSDATE-1' delete;I see no reason for the "alter system switch logfile". In fact you can do something very simple on the Standby :
$ORACLE_HOME/bin/rman target / catalog <user>/<password>@<catalog> << EOF
delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-1';
exit
EOFThis assumes you have doing a backup with RMAN on the Primary ( tested on 11.2.0.2 ) and have this set on the Primary :
CONFIGURE ARCHIVELOG DELETEION POLICY TO APPLIED ON ALL STANDBY;
If you are deleting Archive without using RMAN first then yes something like this ( But I would try to use RMAN and not delete using another method )
echo `date`
echo "Runnung RMAN archive crosscheck"
$ORACLE_HOME/bin/rman <<EOF
connect target /
crosscheck archivelog all;
delete noprompt expired archivelog all;
exit
EOF
echo `date`
Best Regards
mseberg
h2. Another Standby Option
/u01/app/oracle/dba_tool/bin/removestandbyarch.sql
SET echo off
SET feedback off
SET term off
SET pagesize 0
SET linesize 200
SET newpage 0
SET space 0
col name format a120
spool /u01/app/oracle/dba_tool/bin/rm_arch_standby.sh
select 'rm '||NAME from v$archived_log
where REGISTRAR='RFS'
and APPLIED='YES'
and DELETED='NO'
and COMPLETION_TIME < (SYSDATE-10);
SPOOL OFFMain shell script
/u01/app/oracle/dba_tool/bin/removestandbyarch.sh
#!/bin/bash
if [ "$1" ]
then DBNAME=$1
else
echo "basename $0 : Syntax error : use . removestandbyarch <DBNAME> "
exit 1
fi
# Set the Environmental variable for input instance ( ORACLE_SID, ORACLE_HOME path etc )
. /u01/app/oracle/dba_tool/env/${DBNAME}.env
$ORACLE_HOME/bin/sqlplus /nolog <<EOF
   connect / as sysdba
-- spool /u01/app/oracle/dba_tool/bin/rm_arch_${ORACLE_SID}.sh
   @/u01/app/oracle/dba_tool/bin/removestandbyarch.sql
   SPOOL OFF
EOF
echo `date`
# Now run the generated script
echo "Setting permissions and running script"
chmod 740 /u01/app/oracle/dba_tool/bin/rm_arch_standby.sh
. /u01/app/oracle/dba_tool/bin/rm_arch_standby.sh
# Use RMAN to update V$ARCHIVED_LOG.DELETED
echo `date`
echo "Runnung RMAN archive crosscheck"
$ORACLE_HOME/bin/rman <<EOF
connect target /
crosscheck archivelog all;
delete noprompt expired archivelog all;
exit
EOF
echo `date`Edited by: mseberg on Apr 30, 2012 8:40 AM

Primary and physical standby isue

hi guyes,
ia have created physical standby database on the same host as my primary database,i have switch some logs,my standby database was on mount stage. i recovered standby database by being disconnect from session. all the logs are transfered.
but when i tried to shutdown and restart my primar database it gives following errors:-
SQL> startup;
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1247876 bytes
Variable Size 83887484 bytes
Database Buffers 75497472 bytes
Redo Buffers 7139328 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> startup;
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1247876 bytes
Variable Size 83887484 bytes
Database Buffers 75497472 bytes
Redo Buffers 7139328 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open noresetlogs;
alter database open noresetlogs
ERROR at line 1:
ORA-01588: must use RESETLOGS option for database open
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF'
and on asking 'recover database until cancel using backup controlfile'
it ask for the archive log file 35 which is not at the specified place coz no log switch occured after arch log file 34.
how come this?
i have followed complete procedure according to docs....
all 34 arch logs have been applied..
is this happen after creating standby database???
thanks and regards
VD

Vikrant,
If you have applied all the logs
select applied, count(*) from v$archived_log group by applied; -- Please make sure you have all the logs applied successfully
shutdown immediate;
startup force nomount pfile='....' or startup force nomount;
alter database mount standby database;
-- this will activate your standby database and your should be able to open it without any problem; Primary database will be up and running as well.
alter database activate standby database;
alter database set standby database to maximize performance;
alter database open;

Primary database is RAC and Physical standby is single instance

Similar Messages

Maybe you are looking for