Re: ora 600 on linux after failed user level import

zmilos_at_sympatico.ca (zhix) wrote

You can run a DBMS_REPAIR to identify the problem. You can also attempt to export the applicable tables that give the problems, drop them, and then re-create and reload them. As Daniel suggested, it is a good idea to apply the latest 8.1.7.4 patch set.

More detailed info below.

> Oracle8i Enterprise Edition Release 8.1.7.0.1
> Red Hat Linux release 7.2
> Kernel 2.4.7-10 on an i686

> select count(*) from dba_indexes;
> ERROR at line 1:
> ORA-00600: internal error code, arguments: [12700], [2], [4202706],
> [18], [], [], [], []

(from Metalink):
VERSIONS:
7.3.x to 9.x

DESCRIPTION:
Oracle is trying to access a row using its ROWID, which has been obtained from an index.
A mismatch was found between the index rowid and the data block it is pointing to. The rowid points to a non-existent row in the data block. The corruption can be in data and/or index blocks. ORA-600 [12700] can also be reported due to a consistent read (CR) problem.

The information dumped to the trace file varies greatly between releases:
- in Oracle 7.3.x it is ORA-600 [12700][a][b] , where

Arg [a] dba (Data Block Address)
Arg [b] slot number (number of the row in the block pointed by the dba)

• in Oracle 8.x and 9.x, it is ORA-600 [12700][a][b][c] , where Arg [a] dataobj# from sys.obj$ Arg [b] relative dba of the data block Arg [c] slot number of the row in the data block

The arguments of the ORA-600 [12700] contains information obtained from the index we are using.

FUNCTIONALITY:
USER/ORACLE INTERFACE LAYER IMPACT:
POSSIBLE CORRUPTION SUGGESTIONS:
Please refer to [NOTE:155933.1] "Resolving an ORA-600 [12700] error" for additional help with diagnosing this problem.

If the above note does not help, then please log the issue with Oracle Support Services.

Known Issues:
Bug 849963 OERI:12700 possible on DELETE from table with self referencing
FK constraint
Fixed in 8.0.6.0, 8.1.6.3 and 8.1.7.0

Bug 1165009 OERI:12700 possible from DELETE with TRIGGER that issues DML
Fixed in 8.1.7.0

Bug 1679690 Buffer cache in memory corruption (OERI:2032) can lead to permanent data/index mismatch (OERI:12700) Workaround: Recreate the index
Fixed in 8.1.7.2 and 9.0.1.0

> select count(*) from dba_tables;
> ERROR at line 1:
> ORA-00600: internal error code, arguments: [25012], [0], [15], [], [],

(from Metalink)
VERSIONS:
versions 8.0.X to 9.0.X

DESCRIPTION:
We are trying to generate the absolute file number given a tablespace number and relative file number and cannot find a matching file number or the file number is zero.

ARGUMENTS:
Arg [a] Tablespace Number
Arg [b] Relative file number

FUNCTIONALITY:
KERNEL FILE MANAGEMENT TABLESPACE COMPONENT IMPACT:
POSSIBLE PHYSICAL CORRUPTION SUGGESTIONS:
The possibility of physical corruption exists. Obtain the trace files and alert.log for this error and log an iTAR with Oracle Support Services for diagnosis.

Known Issues:

Bug 2531519 CREATE INDEX (WITH PARALLEL) FAILS WITH ORA-600[25012] Fixed in 9.2.0.3

Bug 1788648 ORA-00600[25012] [2147483647] SELECTING FROM V$ TABLES Note that the argument [2147483647] indicates you have encountered this issue.
Fixed in releases 8.1.7.3, 9.0.1.1 and 9.2.0.1

Bug 2212389 ORA-600 [25012] can be reported when a cursor with BINDS gets
aged out and then reloaded
Introduced in Oracle 9i
fixed in releases 9.0.1.4 and 9.2.0.1

Bug 1678963 ORA-600[25012]/ORA-600[4142] possible on TRUNCATE of a table with a CLOB column.
fixed in releases 8.1.7.2 and 9i

Bug 1788648 ORA-600 [25012] [2147483647] possible selecting from certain V$ views.
Fixed in releases 9.0.1.1

--
Billy