This content has been marked as final. Show 9 replies
When you are converting a standby database to primary,the sequence of commmand to execute are:
1:alter database recover managed standby database finish;
2:alter database commit to switchover to physical primary;
5:stop listener to point to crashed db primary and point it to standby and restart.
6:try to connect as user@to_primary
Now, i think it will work fine.
if not please clear out the problem...
Saurabh Kumar Mishra
I have executed command as you said but it gives error( I currently don't have standby logs in standby database), Thanks.
SQL> select open_mode from v$database;
SQL> alter database recover managed standby database finish;
alter database recover managed standby database finish
ERROR at line 1:
ORA-16043: managed recovery session canceled
ORA-16137: No terminal recovery is required
SQL> alter database commit to switchover to physical primary;
alter database commit to switchover to physical primary
ERROR at line 1:
ORA-16139: media recovery required
are both your database,primary and standby belongs to same version?if not then you can not create a standy database atleast with oracle 9i." ora 16137 says that all the archive logs have been applied and there is no current log required to be applied to stdby site." and as far as your ora '16139' error is concerned it says that database did not recoverd throgh the end of the log stream.make sure that entire log stream has been applied.
check out at primary and standby database that if there any logseq between them like if ur primary has a logseq 16 and your standby just showing like 15.i would love to know your reply ragarding success.
Thanks for your entry. When we tested a failover from a single standby database to a new primary we also had the media recovery required error message when issuing the ALTER DATABSE COMMIT TO SWITCHOVER TO PRIMARY';
We followed your instructions, shutdown and restarted the database and all seems OK.
However we had to switch from the standby control file to the original control files before the database would restart. I could not find this step documented in the Oracle manuals.