Media Recovery failed with error 16067

Hi Experts,

I am getting this error in the Alert log of one of my database running in Standby Mode. This standby database is fed from archive logs extracted from my Production server.



ORA-279 signalled during: ALTER DATABASE RECOVER  standby database  ...
Mon Mar 20 04:07:05 2006
ALTER DATABASE RECOVER    CONTINUE DEFAULT  
Media Recovery Log /oracle/P71/saparch/P71arch1_388594.dbf
Errors with log /oracle/P71/saparch/P71arch1_388594.dbf.
Recovery interrupted.
Media Recovery failed with error 16067
ORA-283 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
Mon Mar 20 04:07:05 2006
ALTER DATABASE RECOVER CANCEL
ORA-1112 signalled during: ALTER DATABASE RECOVER CANCEL ...
 

 I can confirm that the archive log /oracle/P71/saparch/P71arch1_388594.dbf is NOT corrupt also I have all the previous and successive log files, is there any way to work around this , I have tried stopping and starting the standby database, however it doesnt help.

Regards,
cryptosid
LVL 5
cryptosidAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

vishal68Commented:
Hi

This error indicates that the Activation ID of the Database and that of the Archive log is not matching. Normally this happens if you recreate the Control file with ResetLogs option, but I have seen some bugs reported where the Activatiob ID got changed even though the Controlfile was recreated with NoResetLogs options.

Did you recreated the Control file of your production instance for any reason ?

Vishal
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cryptosidAuthor Commented:
Hi Vishal,

Thanks for your reply, I did find that there was some mismatch in the Control file of the production and the standby, we recreated the control file from the production for the standby and updated stop/started the standby.

This resolved the issue.

Thanks for your help.

Regards,
cryptosid
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.