ORA-00600 [13004]

ORA-600 [13004] [ID 434203.1]

 

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.7 to 9.2.0.7
This problem can occur on any platform.

Symptoms

You are receiving the following errors in your Alert log while attempting to create an index on a table:
ORA-00600: internal error code, arguments: [13004], [], [], [], [], [], [], []

The Trace file shows the following,
ORA-00600: internal error code, arguments: [13004], [], [], [], [], [], [], []
Current SQL statement for this session:
create index tony_test_mro_ix on mr_orders(order_date)
----- Call Stack Trace -----
ksedmp,kgeriv,kgesiv,ksesic0,qerliRop,qersoFetch,qerliFetch,kdicrws,
kdicdrv,opexe,opiosq0,kpooprx,kpoal8,opiodr,ttcpip,opitsk,opiino,opiodr,
opidrv,sou2o,main

Cause

POSSIBLE BUGS:
---------------------
1) Unpublished Bug 3041474
Abstract: ORA-12801/ORA-600 [13004] ON CREATING INDEX PARALLEL)Status Closed (9.2.0.3, not a Bug)
2) Unpublished Bug 476878
Abstract: ALTER INDEX REBUILD NOPARALLEL
Status Closed ( fixed in 7.3.4.3 and 8.0.3.0 releases)

3) Unpublished Bug 1228658
Abstract: ORA-600 [13004] ON CREATE INDEX ON SNAPSHOT WHEN COMPATIBLE SET TO 8.1.6 Status:  Fixed in 8.1.6.2
The above Bugs are very simiar in their resolutions which follow,
1. Do not create the index using parallelism.
2. Do not create the index on a partitioned table.
3. Do recreate the temporary tablespace with an uniform extent size of 100MB.
You check and determine that you aren't using parallelism to create the index,
the table is not partitioned, and your temporary tablespace is created with an
an uniform extent size of 100MB.

Solution

IMPORTANT:
Check to determine whether the table was created using the 'nologging' option.
If the 'nologging' option was used to create the table, the indexes will not be
created and the ORA-00600 [13004] error is generated.
The resolution to this issue is to create indexes on this table without the 'nologging' option.