ORA-00600 [13013]错误

今天碰到这么个错误：

Errors in file /opt/oraodm/admin/ODPLAT/bdump/odplat_j001_17178.trc:
ORA-00600: 鍐呴儴閿欒?浠ｇ爜, 鍙傛暟: [13013], [5001], [279086], [578959904], [23], [483351996], [17], []

经过查询资料发现下面的内容，这应该是oracle的一个bug，update的时候找不到相应行，重建一下索引就行。

ERROR:
ORA-600 [13013] [a] [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 Code

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

This format relates to Oracle Server 6.0 to 7.3.4

Arg [a] Passcount
Arg 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 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.

Known Issues:
Bug# 2682426 See Note 2682426.8
OERI:13013 from "bitmap AND" of DOMAIN index scans
Fixed: 9.2.0.7, 10.1.0.2

Bug# 1726833 See Note 1726833.8
OERI:13013 / Dump in kdudcp from UPDATE using range scan converted to BITMAPS
Fixed: 8.1.7.3, 9.0.1.1, 9.2.0.1

Bug# 1507392 See Note 1507392.8
OERI:13013 possible from UPDATE of a JOIN VIEW with PARALLELISM
Fixed: 8.1.5.0

Bug# 941018 See Note 941018.8
OERI:13013 on UPDATE/DELETE when predicates resolved fully from BITMAP
Fixed: 8.1.6.3, 8.1.7.0

Bug# 427969 See Note 427969.8
ORA-600 [13013] while updating in a table with triggers
Fixed: 7.3.3.1, 7.3.4.0

[@more@]

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/41451/viewspace-1054524/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/41451/viewspace-1054524/