Recover and opening the database if the archive log required for recovery is missing

Suppose in any case during recovery you dont have the latest archive log file then to counter this situation and open the database by ignoring that missing logfile just follow these steps.screenshots are provided for a better result

Step 1)_Suppose during recovery you came to know that one archive number 120 is missing

Step 2)_As your database is in open mode so create a pfile from the spfile

Step 3)_Add one hidden parameter _ALLOW_RESETLOGS_CORRUPTION=TRUE in the newly created pfile

Step 4)_Shutdown and then mount the database using the newly changed pfile

Step 5)_Perform recovery using backup controlfile;

Step 6)_Open the database using resetlogs options

Step 7)_But as soon as the database gets opened it crashed,it is due the undo tablespace corruption

Step 8)_Again shutdown the database

Step 9)_Change undo management to manual

Step 10)_Then startup using the changed pfile 

Step 11)_Create a new undo tablespace

Step 12)_Shutdown the database

Step 13)_Change the name for the undo tablespace in the pfile

Step 14)_Start the database

Step 15)_Create a spfile from the pfile

Step 16)_Shutdown and startup using the spfile this time

Step 17)_Set undo management to auto

Step 18)_One final time bounce your DB

Step 19)_Finally check the parameters related to undo and also check the archive log

Congratulations!!!

You have successfully start the database which is having a missing archive log file