Monday 7 October 2013

ORA-00600: internal error code, arguments: [kcratr1_lastbwr]

Metlink id *:-ORA-00600:[Kcratr1_lastbwr] During Database Startup after a Crash (Doc ID 393984.1)

SQL> startup
ORACLE instance started.

Total System Global Area 1071333376 bytes
Fixed Size                  1318172 bytes
Variable Size             432014052 bytes
Database Buffers          624951296 bytes
Redo Buffers               13049856 bytes
Database mounted.
ORA-00600: internal error code, arguments: [kcratr1_lastbwr], [], [], [], [],
[], [], [], [], [], [], []

SQL> select open_mode from v$database;

OPEN_MODE
----------
MOUNTED

SQL>



SYMPTOMS
==========
After a disk failure that caused the database to crash, the instance fails to start up with ORA-00600: arguments: [kcratr1_lastbwr].


Error in alert log file is
=============
Tue Oct 08 07:26:53 2013
ALTER DATABASE   MOUNT
Setting recovery target incarnation to 2
Successful mount of redo thread 1, with mount id 3631468477
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE   MOUNT
Tue Oct 08 07:26:57 2013
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
 parallel recovery started with 3 processes
Started redo scan
Errors in file /db/vision/db/tech_st/11.1.0/admin/vision_apps/diag/rdbms/vision/vision/trace/vision_ora_5385.trc  (incident=147332):
ORA-00600: internal error code, arguments: [kcratr1_lastbwr], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /db/vision/db/tech_st/11.1.0/admin/vision_apps/diag/rdbms/vision/vision/incident/incdir_147332/vision_ora_5385_i147332.trc
Aborting crash recovery due to error 600
Errors in file /db/vision/db/tech_st/11.1.0/admin/vision_apps/diag/rdbms/vision/vision/trace/vision_ora_5385.trc:
ORA-00600: internal error code, arguments: [kcratr1_lastbwr], [], [], [], [], [], [], [], [], [], [], []
ORA-600 signalled during: ALTER DATABASE OPEN...
Trace dumping is performing id=[cdmp_20131008072701]
Tue Oct 08 07:27:55 2013
Sweep Incident[147332]: completed


Solution: Meta link says.
=====================
Mount the database and issue a recover statement.


SQL> recover database;
Media recovery complete.
SQL> select open_mode,name from v$database;

OPEN_MODE  NAME
---------- ---------
MOUNTED     VISION

SQL>

SQL> alter database open;

Database altered.

SQL> select status from v$instance;

STATUS
------------
OPEN
SQL> select open_mode,name from v$database;

OPEN_MODE  NAME
---------- ---------
READ WRITE VISION


SQL>

Quote of the day !!!
Our greatest weakness lies in giving up. The most certain way to succeed is always to try just one more time.

3 comments: