This question needs to be asked in Data Guard section.
I think the standby db is not in sync with the primary. Can you check the last applied seq# in standby and the current seq# in primary and make it in sync and try opening the db.
If its not in sync and the required archive logs are missing, you can rollforward the standby using rman incremental backup from primary.
HI Anand, The standby is in sync with primary.As i have mentioned earlier it keeps asking for the current log file of the primary database no matter how many log switches I give.I tested it in 18.104.22.168 and it works fine. I have a hunch that the problem lies because standby crash recovery is starting recovery in real time mode when i give ALTER DATABASE OPEN.Any idea on how to stop this?Any body having a current working setup in 22.214.171.124 PSU 7
Hi Frak, Yes the maximum sequence no is same in both primary and standby.Only the current redo log is not shipped to standby.Unfortunately I cannot post alert log..these are the contents as seen
Alter database recover managed standby database cancel Completed:Alter database recover managed standby database cancel alter database open This instance was first to open Beginning standby crash recovery serial media recovery started Managed standby recovery starting real time apply Media recovery waiting for thread 1 sequence 108 => this is the current logfile
After this i issued 2 log switches in primary .
The logs were transfered and they were applied in standby
Again it started waiting for the current logfile this time 110.
If no log is provided for a minute it comes out with the following error
wait timeout:thread 1 sequence 110 standby crash recovery aborted due to error 16016 Ora-10458:standby database requires recovery ORA-01195:online backup of file 1 needs more recovery to be consistent
I will uploads the pics of alert log too
create standby redo logfiles on both primary and standby and see if you still get the error. Also let us know what is the protection mode of the db and value set for log_archive_dest_2
refer the below link to create and understand more on Standby redo logfile --
1) Have you created standby redo logs? if not have a lookie here: Creating a Physical Standby Database
2) If yes, start mrp with: alter database recover managed standby database using current logfile parallel 10 disconnect from session;
3) Then, try to do a: alter database open read only
4) You appear to have incorrect tnsnames entries for your FAL_SERVERS (h113racs and h213racs). Are those other standby ?
It shows redo fetching using fal_client is failing , fal is used to fetch missing archived logs
For 12154 - you will never regret spent time on reading this ora-12154/tns-03505 | Ed Stevens, DBA
What is the output of archive log list on primary/standby?
Can you check primary log alert logfile if its able to send archive to standby
Have you set fal_client parameter explicity?
what about fal_server?
This looks like RAC to me. Could you please post the O/P of the below queries when run on the primary and the standby DB?
SQL>select thread#,max(sequence#) from v$archived_log group by thread#,
SQL>select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;