ORA-600 INTERNAL ERROR CODE

[Former Member]

Hi folks,

Due to deadlock issue in BW ehp1 systemBelow error codes generated in trace file

- ORA-00600: internal error code, arguments: [13013], [5001], [859724], [193618620], [2], [193618620], [17], [], [], [], [], [].

Please any one suggest  on how to  proceed for further investigation.

Regards,

Sharma TvK

[former_member207463]

Please check note 1868324 about Handling ORA-600/ORA-7445 error.

[former_member206552]

hi sharma,

it is always a good idea to be on the latest levels,

why do you not go to 11.2.0.3?

best regards

marius

[former_member206552]

hi sharma,

do you have the latest oracle patch bundle installed ?

please have a look at the following

http://oraclemamukutti.blogspot.de/2011/06/ora-00600-13013-5001.html

best regards

marius

[Former Member]

Hi,

PSU 11.2.0.2.3  was applied  last year. I have checked the above blog.

Is there any way to avoid deadlocks  during extractions in BW.

Please suggest.

Regards,

Sharma TvK

[former_member206552]

hi sharma,

for deadlocks please try the following note

SAP Note 631668 - DEADLOCK

best regards

marius

[former_member206552]

hi sharma,

for the ORA-00600 please see below this is from oracle

New and Improved: ORA-600 [13013] "Unable to get a Stable set of Records" [ID 1438920.1]

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

PURPOSE:

This article is a new and improved copy of OERI Note: 28185.1 which is designed to pilot a new feature to help identify known bugs for ORA-600[13013] issues. If you do not want to use the new feature, please use the original Note: 28185.1.

The new feature available in this version of the OERI note provides a list of conditions most commonly identified for bugs related to this error. These conditions can be used to narrow down the possible cause of the error. Our goal with this pilot is to determine if this level of detail will lead our readers to a quicker resolution. After having used this new feature, please email Vickie.Carbonneau with your feedback. Please provide answers to the following:

◦Did this new feature help you identify the issue?
◦Did it save you research time?
◦Do you feel more confident with applying a patch/patch set or using the workaround(if provided)?
◦Would you use this new feature again?
This article has been published because the ORA-600 error has been reported in at least one confirmed bug.

ERROR:

Format: ORA-600 [13013] [a] [b] [c] [d] [e] [f]

VERSIONS:

versions 6.0 and above

DESCRIPTION:

During the execution of an UPDATE statement, after several attempts (Arg [a] passcount) we are unable to get a stable set of rows that conform to the WHERE clause.

ARGUMENTS:

The number of arguments and their meaning vary depending on the Oracle
Server release and the object types relating to the error.

2 Argument format
=================

This format relates to Oracle Server 8.0.4 and above and Index Only Tables (IOT)

Arg [a] Passcount
Arg [b] Code

5 Argument format
=================

This format relates to Oracle Server 6.0 to 7.3.4

Arg [a] Passcount
Arg [b] Code
Arg [c] Tablespace Decimal Relative DBA (RDBA) of block containing the row to be updated
Arg [d] Row Slot number
Arg [e] Decimal RDBA of block being updated (Typically same as [c])

6 Argument format
=================

This format relates to Oracle Server 8.0.3 and above

Arg [a] Passcount
Arg [b] Data Object number
Arg [c] Tablespace Decimal Relative DBA (RDBA) of block containing the row to be updated
Arg [d] Row Slot number
Arg [e] Decimal RDBA of block being updated (Typically same as [c])
Arg [f] Code

FUNCTIONALITY:

Update Execute

IMPACT:

PROCESS FAILURE
POSSIBLE INDEX CORRUPTION

SUGGESTIONS:

This error could indicate a corrupt index.

Check for corrupted indices using the following command :

ANALYZE TABLE <table_name> VALIDATE STRUCTURE CASCADE;

Where <table_name> is the table being updated.

Drop and recreate any indexes that show problems.

On Parallel Server instances (OPS - Oracle Server &lt;= 7.X) this can be due to an inappropriate setting of max_commit_propagation_delay. Setting this parameter to 0 can avoid this error.

For 7.3.2 releases please see ALERT: 40673.1 ALERT: Incorrect Results or Internal Errors from Indexed Table Access

If the Known Issues section below does not help in terms of identifying a solution, please submit the trace files and alert.log to Oracle Support Services for further analysis.

KNOWN BUGS:

[Former Member]

Hi Marius,

Thanks for the detailed information.

If we apply Latest oracle patches  of 11.2.0.2 , will it resolve  the above ora-00600 error.

Any further information much appreciated.

Regards,

sharma TvK