Even if it's difficult to be in such a position, if you can't open your database because it needs recovery and you don't have archivelogs to recover or a cold backup to restore, this situation does not mean you'll say 'bye bye' to your database.
There is an undocumented parameter "_allow_resetlogs_corruption" that you can use in this situation. Setting this parameter TRUE in init.ora file may help you save (maybe not all) data. Procedure includes backing up the database, opening it with the updated pfile, discover the problematic data and try to recover all you can...
Here is a detailed article about the use of _allow_resetlogs_corruption parameter. Thanks to Terry Sutton, the author, for this very useful article which covers this lifesaver topic systematically.
Do not forget that you should not use an undocumented parameter without the support of Oracle.

5 Responses so far.

  1. sushma says:

    Hey Really Thanks for sharing the best information regarding category, hope you will write more great blogs.
    Oracle Fusion Financials Online Training

  2. Sravani says:

    Thank you for sharing such a nice and interesting blog with us. I have seen that all will say the same thing repeatedly. But in your blog, I had a chance to get some useful and unique information.

    Oracle Fusion HCM Online Training

  3. Santhosh says:

    I would like to thank you for the efforts you have made in writing this article. I am hoping the same best work from you in the future as well.

    Oracle Fusion SCM Online Training

  4. harsha says:

    Really thanks for sharing such a wonderful blog.
    Oracle Fusion Financials Online Training

  5. Naga says:

    Very interesting blog, keep posting such an informative post.

    Oracle Fusion Financials Online Training

Powered by Blogger.

Page Views

- Copyright © Emre Baransel - Oracle Blog -Metrominimalist- Powered by Blogger - Designed by Johanes Djogan -