New Features for DBA’s

Subscribe to Posts by Email


 

Subscriber Count

    696

Disclaimer

All information is offered in good faith and in the hope that it may be of use for educational purpose and for Database community purpose, but is not guaranteed to be correct, up to date or suitable for any particular purpose. db.geeksinsight.com accepts no liability in respect of this information or its use. This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content and if notify any such I am happy to remove. Product and company names mentioned in this website may be the trademarks of their respective owners and published here for informational purpose only. This is my personal blog. The views expressed on these pages are mine and learnt from other blogs and bloggers and to enhance and support the DBA community and this web blog does not represent the thoughts, intentions, plans or strategies of my current employer nor the Oracle and its affiliates or any other companies. And this website does not offer or take profit for providing these content and this is purely non-profit and for educational purpose only. If you see any issues with Content and copy write issues, I am happy to remove if you notify me. Contact Geek DBA Team, via geeksinsights@gmail.com

Pages
«  
  »

ORA-00600: internal error code, arguments: [kcratr1_lostwrt].

Hello,

Here is one the knowledge share that has been posted by Sarma. Many thanks to him for his enthusiastic contribution.

ORA-00600: internal error code, arguments: [kcratr1_lostwrt].

 

As per 351678.1, the last block written was lost when the instance crashed. On startup, Oracle checks the last version of the block written to disk; if an old block is found, the ORA-600 [kcratr1_lostwrt] is raised.

To fix this,

SQL> shutdown immediate;
SQL> startup mount;
SQL> recover database;
SQL> alter database open;

All happy!!! You may need to have latest online redo log files or even archive to made this happy.

If you do not have archives/redo then you may need to consider this alternative way.

add the _allow_resetlogs_corruption=true –>  to parameter and to skip redo log/archives

Startup the database in mount state

SQL> startup mount

ORACLE instance started.

SQL recover database until cancel; –> Recover no possibility –> Recover will fail no archives etc etc

SQL> Alter Database open resetlogs; or just alter database open

 

Hope this is helpful to you

-Thanks

Geek DBA

January 17th, 2013 | Tags: , | Category: Administration

Comments are closed.