Thursday, 27 August 2009

WARNING! Recovering data file 1 from a fuzzy file. If not the current file

Introduction:

We use EMC BCV feature to clone our production database, and it was all working fine, but suddenly we started getting the errors , on recovery process. Following were the errors..

"WARNING! Recovering data file 1 from a fuzzy file. If not the current fileit might be an online backup taken without entering the begin backup command."

Troubleshooting and Resolution:

It was very interesting situation, as the same process which we were following was not working suddenly, our team tried the same procedure twice and every time they got the errors on recovery process. And we were following the below BCV cloning procedure.

Steps for cloning by use of BCV:

1- put the production database in backup mode.

2- sync the BCV volumes.

3- split the BCV volumes.

4- take the production database out of backup mode.

5- start the recovery on the cloned database.

6- open the database after successfull recovery.


We tried twice with the same proceudre but we were getting following errors..
---------------------------------------------
ALTER DATABASE RECOVER database using backup controlfile until cancel
Wed Aug 6 13:03:00 2009
Media Recovery Start
WARNING! Recovering data file 1 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 2 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 3 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 4 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 5 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
---------------------------------------------

and we opend the cases with Oracle and EMC, but the error was showing some thing not correct with some of the procedure, either the production database didnt go properly in the backup mode, but when we checked the alert log, the database went to backup mode correctly, and it came out of the backup mode properly. Having seen the alert log, we suspected that something went wrong with BCV etc. But we were not sure, as we didnt get any error messages during the BCV sync and split.

Then we decided to give a one more try with the same procedure, and when we checked the team, they were not following the listed procedure, as they were doing split of the BCV after taking the database out of backup mode, whereas they should have done the split before the database taken out of backup mode. When we followed the same listed procedure, every thing was ok, and we were able to do successfull recovery of the database and able to open the database. :)








3 comments:

Henry MH said...

I also faced the problem. Now awaiting system admin to verify.

Thank you very much for post and sharing this peice of information.

Fri Aug 27 09:20:32 2010
Media Recovery Start
WARNING! Recovering data file 358 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 359 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 360 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 361 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 470 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 472 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 473 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 476 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 477 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 478 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 479 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 480 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 481 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
WARNING! Recovering data file 484 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.

akshya said...

i am also facing the same warnings in my database alert log after refresh from production with the same method you mentioned in your blog .
but able to recover and open the database.

is there any impact on the database due to this warning..

Mehmood Ur Rehman said...

Dear Akshay

if you are following the steps which I listed, and you have the same enviornment / architecture then the database should be recover, please do discuss with your system / unix / emc admin.

best regards