Tuesday 29 July 2014

ORA-00600: internal error code, arguments: [kcratr_nab_less_than_odr], [1], [65], [52510], [52529], []

ORA-00600 internal error code:

This error code is native to internal exceptions from the Oracle programs. It
indicates that the process has encountered an unexpected problem. It may be
due to:
Timeout
A corrupted file
A crash that has affected stored data
I/O issue "(physical memory)"















ORA-00600: internal error code resolved:



SQL> alter database open
  2  ;
alter database open
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [kcratr_nab_less_tha
[65], [52510], [52529], [], [], [], [], [], [], []

THIS ERROR IS DUE TO INVALID ENTRY IN THE CONTROL FILE:

SOLUTION TO  ORA-00600:

IT IS BETTER TO CREATE A NEW CONTROL FILE.

FIRST CHECK IF CONTROL FILE EXIST OR NOT?

SQL>STARTUP NOMOUNT

SQL> ed a.sql


IF THERE WILL BE A CONTROL FILE THEN IT WILL OPEN. NOW INSIDE CONTROL FILE CHECK THE LOCATION OF:
REDO LOGS
SYSTEM FILE
SYSAUX FILE
UDO FILE
USER FILE

FINALLY DELETE OR BACKUP OLDER CONTROL FILE AND RECREATE NEW ONE USING:
SQL>@ a.sql

CASE 2: IF CONTROL FILE DOESN'T EXIST THEN RECREATE NEW ONE:

SQL>SHUT IMMEDIATE
SQL>STARTUP MOUNT
SQL> alter database backup controlfile to trace
  2  ;

Database altered.

SQL> shutdown abort
ORACLE instance shut down.
SQL> startup nomount
ORACLE instance started.

Total System Global Area  606806016 bytes
Fixed Size                  1376268 bytes
Variable Size             385880052 bytes
Database Buffers          213909504 bytes
Redo Buffers                5640192 bytes
SQL> ed a.sql
DELETE OLDER CONTROL FILE BEFORE CREATING NEW ONE:
SQL> @ a.sql

Control file created.

SQL> ALTER DATABASE OPEN RESETLOGS;

Database altered.

SQL> SELECT OPEN_MODE FROM V$DATABASE;

OPEN_MODE
--------------------
READ WRITE


No comments:

Post a Comment