ORA-00600: internal error code, arguments ... is a problem due to disc access ?

[Jdamian]

Hi, a database running in my box crashed. In alert.log is found the following error messages:

Wed Jul 2 16:18:09 2003
Thread 1 advanced to log sequence 83976
Current log# 8 seq# 83976 mem# 0: /sibd1/sgbd/oracle/redo/log8_siebeldb.log
Wed Jul 2 16:18:09 2003
ARC1: Beginning to archive log# 7 seq# 83975
Wed Jul 2 16:34:33 2003
Errors in file /sibd1/sgbd/oracle/8i/admin/bdump/lgwr_15175_siebeldb.trc:
ORA-00600: internal error code, arguments: [2103], [0], [0], [1], [900], [], [], []
Wed Jul 2 16:34:37 2003
Errors in file /sibd1/sgbd/oracle/8i/admin/bdump/lgwr_15175_siebeldb.trc:
ORA-00600: internal error code, arguments: [2103], [0], [0], [1], [900], [], [], []
Wed Jul 2 16:34:37 2003
LGWR: terminating instance due to error 600
Instance terminated by LGWR, pid = 15175

DataBase admin hint this error is due to problems to access disc...
This disk is a LUN residing on a XP512. In this XP512 other five databases are running with no problem ...

what do you think ?

[Massimo Bianchi]

Hi, a good note from metalink:

it looks like a over-charged moment.


PURPOSE: This article discusses the internal error "ORA-600 [2103]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR: ORA-600 [2103][a][b][c][d] VERSIONS: versions 7.3.X through 9.x DESCRIPTION: Oracle is attempting to acquire an enqueue. If this operation times out, an ORA-600 [2103] error is reported. There are three formats of this error depending on Oracle release and operation. Each format is identified by the number of additional arguments. Prior to Oracle Server release 7.3.4 (one additional argument) ------------------------------------------------------ ORA-600 [2103] [a] Meaning: Oracle has waited too long for the control file enqueue. ARGUMENTS: Arg [a] Time out - the time waited for the enqueue, in seconds. (normally 900 seconds ie 15 Minutes) From Oracle 7.3.4 through 9.x (4 additional arguments) -------------------------------------------------------- ORA-600 [2103] [a] [b] [c] [d] Meaning: Oracle has waited too long for the control file enqueue. This error has the same meaning as the single argument case above - we simply output additional information. ARGUMENTS: Arg [a] 1 (Read only indicator - 0 for updates, 1 for read only) Arg [b] 0 (Type indicator - 0 and 4 for ENQUEUE) Arg [c] 1 (Wait indicator - 1 indicates we should wait for the request) Arg [d] Time out - the time waited for the enqueue, in seconds. (normally 900 seconds ie 15 Minutes) Oracle Server Release 9.x ------------------------- ORA-600 [a] [b] Meaning: Oracle is trying to write a Checkpoint Progress record and has waited too long for the enqueue. ARGUMENTS: ORA-600 [a] [b] --------------- Arg [a] 1 (Wait indicator - 1 indicates we should wait for the request) Arg [b] 256 (indicates we skip to the front of the convert queue) FUNCTIONALITY: CONTROL FILE MANAGEMENT COMPONENT IMPACT: Possible Instance Failure SUGGESTIONS: Check the alert log to see how often a logfile switch is taking place. Try and ensure that REDO log files are sized such that a log switch takes place approximately every half hour during heavy load. This will reduce the number of times we need to obtain the control file enqueue. Tune your datafile layout to resolve I/O contention. Check with the Hardware vendor to ensure there are no hardware problems and that you are on the latest OS patch level. In the case of IBM, see [NOTE:1058194.6] to obtain the correct OS patch. Known issues: Bug:1223914 OERI:2103 Concurrent ALTER TABLESPACE READ WRITE/READ ONLY Fixed in Oracle releases 8.1.6.3 and 8.1.7.0 Bug:1390375 DEFUNCT CHECKPOINT PROCESS HOLDS LOCK CAUSING ORA-600 [2103] An AIX port specific issue. (Note:1058194.6)

HTH,
Massimo

[Massimo Bianchi · Accepted solution]

Hi again... better output :)


Note: For additional ORA-600 related information please read [NOTE:146580.1]

PURPOSE:

This article discusses the internal error "ORA-600 [2103]", what
it means and possible actions. The information here is only applicable
to the versions listed and is provided only for guidance.

ERROR:
ORA-600 [2103][a][b][c][d]

VERSIONS:
versions 7.3.X through 9.x

DESCRIPTION:

Oracle is attempting to acquire an enqueue.

If this operation times out, an ORA-600 [2103] error is reported.

There are three formats of this error depending on Oracle release and
operation. Each format is identified by the number of additional
arguments.

Prior to Oracle Server release 7.3.4 (one additional argument)
------------------------------------------------------

ORA-600 [2103] [a]

Meaning: Oracle has waited too long for the control file enqueue.

ARGUMENTS:

Arg [a] Time out - the time waited for the enqueue, in seconds.
(normally 900 seconds ie 15 Minutes)

From Oracle 7.3.4 through 9.x (4 additional arguments)
--------------------------------------------------------

ORA-600 [2103] [a] [b] [c] [d]

Meaning: Oracle has waited too long for the control file enqueue.
This error has the same meaning as the single argument
case above - we simply output additional information.

ARGUMENTS:

Arg [a] 1 (Read only indicator - 0 for updates, 1 for read only)
Arg [b] 0 (Type indicator - 0 and 4 for ENQUEUE)
Arg [c] 1 (Wait indicator - 1 indicates we should wait for the request)
Arg [d] Time out - the time waited for the enqueue, in seconds.
(normally 900 seconds ie 15 Minutes)

Oracle Server Release 9.x
-------------------------

ORA-600 [a] [b]

Meaning: Oracle is trying to write a Checkpoint Progress record and has
waited too long for the enqueue.

ARGUMENTS:

ORA-600 [a] [b]
---------------

Arg [a] 1 (Wait indicator - 1 indicates we should wait for the request)
Arg [b] 256 (indicates we skip to the front of the convert queue)

FUNCTIONALITY:
CONTROL FILE MANAGEMENT COMPONENT

IMPACT:
Possible Instance Failure

SUGGESTIONS:

Check the alert log to see how often a logfile switch is taking place.

Try and ensure that REDO log files are sized such that a log switch
takes place approximately every half hour during heavy load. This will
reduce the number of times we need to obtain the control file enqueue.

Tune your datafile layout to resolve I/O contention.

Check with the Hardware vendor to ensure there are no hardware problems
and that you are on the latest OS patch level.

In the case of IBM, see [NOTE:1058194.6] to obtain the correct OS
patch.

Known issues:

Bug:1223914 OERI:2103 Concurrent ALTER TABLESPACE READ WRITE/READ ONLY
Fixed in Oracle releases 8.1.6.3 and 8.1.7.0

Bug:1390375 DEFUNCT CHECKPOINT PROCESS HOLDS LOCK CAUSING ORA-600 [2103]
An AIX port specific issue. (Note:1058194.6)


Massimo

[Yogeeraj_1]

hi,

You will have to "resize" your redolog files.

Normally, you will have to figure out your redo generation rate and use that to help you size it. I generally just add logs until it goes away. Not very scientific but brutally effecient.

I myself start with 3 groups of 2 members of 25meg apiece and work up from there. Either adding more groups or making the members larger until I have enough online redo log to get me through at least 15-20 minutes of work without switching. As with all rules of thumb -- there will be times when 15-20 minutes is too long and too short. You need to pick your time and go from there.

hope this helps!

regards
yogeeraj

[julialloyds45]

ORA-00600: internal error code, arguments ...is a generic internal error number for Oracle program exceptions. It is an indication that the process has encountered a low level, unexpected condition. You can fix this error manually without taking help of third party repair tool. But any small mistake can permanently delete your data stored in it so it is recommended to take help of Oracle Database repair Tool without affecting the stored data and data objects like table, macros etc.  

For More Information: http://oracle.filerepairtool.net/blog/fix-ora-00600-error 

[Moderator edit: Removed the broken link.]