cancel
Showing results for 
Search instead for 
Did you mean: 

ora-00600

jonax
Occasional Contributor

ora-00600

Hi!!

I continuesly received an ora-00600 error in my alert log. The version of my oracle is 9.2.0 64 bit.

ORACLE Instance PROD (pid = 7) - Error 600 encountered while recovering transaction (18
, 46) on object 21036.
Thu Aug 25 04:58:39 2005
Errors in file /opt/oracle/admin/prod/bdump/prod_smon_8391.trc:
ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], []
Thu Aug 25 04:59:00 2005
SMON: mark undo segment 18 as needs recovery
SMON: about to recover undo segment 18
Thu Aug 25 04:59:13 2005
Errors in file /opt/oracle/admin/prod/bdump/prod_smon_8391.trc:
ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], []


Please provide me the steps/procedure on how to resolve this kind of error.

Thank you,

jonax

5 REPLIES
Rick Garland
Honored Contributor

Re: ora-00600

An ora-600 error can have numerous causes.

Best bet is to open a tar with Oracle.

Indira Aramandla
Honored Contributor

Re: ora-00600

Hi Jonax,

ORA-600 Internal error with arguments 6000 onwards means, "The data layer is responsible for maintaining and managing the data in the database tables and indexes. Issues in this area may indicate some kind of physical issue at the object level and therefore, it is important to try and isolate the object and then perform an analyse on the object to validate its structure".

It could be data, analyze command and index related activity

In the error that you encountered, "Error 600 encountered while recovering transaction ((8,46) on object 21036".

If there are no other errors in the trace file

Then query the dba_objects to find the object_name for the object_id reported in the error message
Eg:-
SQL>select object_name, object_type, owner from dba_objects where
object_id=21036;

If the object_name is an index then rebuild the index and this may resolve the problem.

Indira A
Never give up, Keep Trying
Indira Aramandla
Honored Contributor

Re: ora-00600

Hi again,

I found a similar thread issue in Metalink.

where the object is reported in the error message was 3470 and the object name was found to be 'fnd_concurrent_requests_n7';

This was the reply for that.

This error sequence occurs when Oracle is undoing an index leaf operation and the key is not found. It usually is caused by a media corruption problem (lost write problem or disk corruption).

You could try rebuilding the corrupted/problem index.

Otherwise you can
1) Restore a backup (cold or HOT) on another machine.
2) Run DBVERIFY (dbv executable) against all the backup datafiles involved.
3) Recover and roll forward with the archive logs through the time when the error occurred. If there are no errors, this is most likely a lost I/O or media corruption. You will need to get with your Hardware vendor and check the hardware/Operating system with extensive diagnostics.

You should file an iTAR to get more specific assistance on getting this scenario corrected


IA
Never give up, Keep Trying
Yogeeraj_1
Honored Contributor

Re: ora-00600

hi jonax,

the right steps/procedure is to log a tar with Oracle on Metalink. Of course, you must be having a support contract with them to be able to access this site.

You may also read metalink note: 146580.1

It could be related to a corrupted index which you have to rebuild.


kind regards
yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
Steven E. Protter
Exalted Contributor

Re: ora-00600

ORA-0600 is the Oracle error of last resort. It means something serious is wrong, but the software has no idea what the problem is.

Its important in these circumstances to try and track down exactly whats happening when the error occurs.

Fortuneately you have some clues in the error text. SMON is having trouble and there may be some data in the trc file.

I would see if there is adequate shared memory allocated and if the SGA settings are appropriate for the way you are using the database.

I would also check your shutdown routines to see if the database is shutting down normally or crashing. A recovery should not be happening after every time you brint down your database to do a backup.

SEP
Finally got internet in the home .!!!
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com