In the file: "suelen.txt" I see this error message:
ORA-00600: internal error code, arguments: [13013], [5001]...
An ORA-00600 error is never a good thing. Check the alert.log file on your Oracle server for more information, if any.
You may need to open a Service Request with Oracle on this if the following info from the "ORA-600 Lookup" section of Oracle's MetaLink site does not solve the problem for you. Here is what I copied from MetaLink:
Subject: ORA-600 [13013] "Unable to get a Stable set of Records"
Doc ID: 28185.1 Type: REFERENCE
Modified Date : 02-APR-2009 Status: PUBLISHED
Note: For additional ORA-600 related information please read Note 146580.1
PURPOSE:
This article discusses the internal error "ORA-600 [13013]", 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 [13013] [a] [b] [c] [d] [e] [f]
VERSIONS:
versions 6.0 to 10.1
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 to 10.1 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 Relative DBA of block containing the row to be updated
Arg [d] Row Slot number
Arg [e] Relative DBA of block being updated (should be same as [c])
6 Argument format
=================
This format relates to Oracle Server 8.0.3 to 10.1
Arg [a] Passcount
Arg [b] Data Object number
Arg [c] Tablespace Relative DBA of block containing the row to be updated
Arg [d] Row Slot number
Arg [e] Relative DBA of block being updated (should be 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
VALIDATE STRUCTURE CASCADE;
Where is the table being updated.
Drop and recreate any indexes that show problems.
On Parallel Server instances (OPS - Oracle Server <= 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.
