Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I want my DB to stop instance recovery during opening, how to do it?

I want it because it crashes when trying to do instance recovery, I am testing some cases and want to disable it

Is there any possibility?

share|improve this question
1  
What is the reason your database needs instance recovery?Before proceeding any further you need to ask yourself why you wanna continue with an inconsistent database?? –  steve Oct 19 '11 at 4:50
    
@steve exactly. –  Jack Douglas Oct 19 '11 at 7:48
    
The reason is that 4 blocks in one datafile(that is not system datafile) is corrupted, and Oracle is trying to recover them but crashes after server tries(as I found it is caused by a bug in 10.2.0.4). I want my DB to start normally without trying recovery and I will recover that blocks myself from backup, or will move that object to another tablespace. –  kupa Oct 27 '11 at 19:37

1 Answer 1

up vote 5 down vote accepted

Instance Recovery is necessary to get the database back to a consistent state after shutdown abort or some other abnormal shutdown event. Oracle is never going to let you open the database in an inconsistent state, so no, there is no possibility that you can disable it. If Oracle is crashing during Instance Recovery you need to get in touch with Oracle Support or revert to a backup.

The concepts guide has essential reading about instances and more particularly what Instance Recovery is and why it is sometimes needed:

If an instance of an open database fails, either because of a SHUTDOWN ABORT statement or abnormal termination, then the following situations can result:

  • Data blocks committed by a transaction are not written to the data files and appear only in the online redo log. These changes must be reapplied to the database.

  • The data files contains changes that had not been committed when the instance failed. These changes must be rolled back to ensure transactional consistency.

Instance recovery uses only online redo log files and current online data files to synchronize the data files and ensure that they are consistent.

If the Instance Recovery crash is caused by a corrupt datafile you could mount the instance, drop the offending datafile and then open the database - but you will lose the tablespace that file is in.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.