[8i]ORA-00600 lors d'un export

**neo.51** · 15/04/2005, 16h14

Bonjour,

Voilà, je souhaite exporter une base oracle 8i. J'ai déjà exporté cette base plusieurs fois sans aucun problèmes.

Mais aujourd'hui voilà, quand je veux exporter ma base :

Code :

Sélectionner tout - Visualiser dans une fenêtre à part

1
2
EXP-00056 : Erreur oracle 600
ORA-00600 : code erreur interne arguments : [25012],[6],[32],[],[],[],[]

ce méssage ne se produit que sur une de mes 53 tables, les autres s'exportent sans aucun soucis.

si j'éssaye d'exporter cette table "à part" je récupère le même méssage d'érreur. J'ai été voir la documentation oracle, et le ORA-00600 c'est pas le code d'érreur le plus sympas

comment me sortir de ce mauvais plan ?

**orafrance** · 15/04/2005, 16h38

Apparemment c'est un bug :

1228658 This problem was introduced in 8.1.6.0 Create INDEX on a snapshot / MVIEW can produce a corrupt index. This may show up as ORA-600 [13004] or an ORA-600 [25012] or ANALYZE TABLE snapshot_name VALIDATE STRUCTURE CASCADE reporting ORA-1499. This can easily occur if the index can be built from an existing index on the snapshot.

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

PURPOSE:
This article discusses the internal error "ORA-600 [25012]", 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 [25012] [a] [b]

VERSIONS:
versions 8.0 to 10.1

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# 3751874 See Note 3751874.8
OERI[25012] can occur when _old_connect_by_enabled set to true
Fixed: 9.2.0.6, 10.1.0.4, 10.2

Bug# 3430832 See Note 3430832.8
OERI[25012] in DML after ONLINE create index against PARTITIONED table
Fixed: 9.2.0.6, 10.1.0.3, 10.2

Bug# 3258674 See Note 3258674.8
QMN process may dump or raise an internal error during DML
Fixed: 9.2.0.7, 10.1.0.4, 10.2

Bug# 3150268 See Note 3150268.8
OERI[kcbgcur_1] / OERI:25012 deleting rows from PARENT table with LIST subpartitions
Fixed: 9.2.0.5, 10.1.0.2

Bug# 3070856 See Note 3070856.8
OERI:12700 / 25012 / ktrexc_1 on transported tablespace with SMU
Fixed: 9.2.0.5, 10.1.0.2

Bug# 2531519 See Note 2531519.8
OERI:[25012] from parallel direct load of bitmap managed segments
Fixed: 9.2.0.3, 10.1.0.2

Bug# 2526334 See Note 2526334.8
OERI:25012 from AND EQUAL with B-Tree and DOMAIN index
Fixed: 9.2.0.3, 10.1.0.2

Bug# 2287815 See Note 2287815.8
OERI:KTSPISCHNT / OERI:25012 after exchange PARTITION with bitmap managed segments
Fixed: 9.0.1.4, 9.2.0.1

Bug# 2214167 See Note 2214167.8
OERI:25012 / wrong results possible after TRUNCATE of bitmap managed index
Fixed: 9.0.1.4, 9.2.0.1

Bug# 2212389 See Note 2212389.8
OERI:25012 / Cursor frame memory corruption when cursor with BINDS aged out / reloaded
Fixed: 9.0.1.4, 9.2.0.1

Bug# 2189615 See Note 2189615.8
OERI:25012 / OERI:504 [cache buffers chains] selecting from certain V$ tables
Fixed: 8.1.7.4, 9.0.1.4, 9.2.0.1

Bug# 2184731 See Note 2184731.8
OERI:25012 possible from index prefetch
Fixed: 8.1.7.4, 9.2.0.1

Bug# 1968815 See Note 1968815.8
OERI:25012 possible from SMON following DROP TABLESPACE command
Fixed: 9.0.1.2, 9.2.0.1

Bug# 1949273 See Note 1949273.8
OERI:25012 / ORA-1555 / ORA-22922 accessing LOB data after ALTER TABLE MOVE lob
Fixed: 8.1.7.3, 9.0.1.0

Bug# 1872985 See Note 1872985.8
Dump / OERI:25012 from BITMAP CONVERSION of INDEX on GLOBAL TEMPORARY TABLE
Fixed: 9.0.1.2, 9.2.0.1

Bug# 1837529 See Note 1837529.8
OERI:KFTR2BZ_1/OERI:25012 from CREATE sub-partitioned local INDEX ONLINE
Fixed: 8.1.7.3, 9.0.1.1, 9.2.0.1

Bug# 1834530 See Note 1834530.8
OERI:25012 / wrong results after EXCHANGE PARTITION with indexes with different FREELIST /FREELIST GROUPS
Fixed: 8.1.7.4, 9.0.1.4, 9.2.0.1

Bug# 1788648 See Note 1788648.8
OERI:25012 [2147483647] possible selecting from certain V$ views
Fixed: 8.1.7.3, 9.0.1.1, 9.2.0.1

Bug# 1784708 See Note 1784708.8
OERI:KCBGTCR_1/OERI:25012 accessing LONG / LONG RAW in a HASH CLUSTER
Fixed: 8.1.7.3, 9.0.1.1, 9.2.0.1

Bug# 1698789 See Note 1698789.8
Wrong results, ORA-1410, ORA-8103, OERI:25012 on SELECT of UNSCOPED REF with ROWID
Fixed: 9.2.0.1

Bug# 1678963 See Note 1678963.8
OERI:25012 / OERI:4142 possible on TRUNCATE of a table with a CLOB column
Fixed: 8.1.7.2, 9.0.1.0

Bug# 1527982 See Note 1527982.8
OERI:25012 / Bitmap index<->table mismatch after UPDATE of PARTITION KEY moves rows
Fixed: 8.1.7.2, 9.0.1.0

Bug# 1396571 See Note 1396571.8
OERI:25012 possible importing with TRANSPORT_TABLESPACE=Y
Fixed: 8.0.6.3, 8.1.6.3, 8.1.7.1, 9.0.1.0

Bug# 1312233 See Note 1312233.8
OERI:25012 / OERI:KCBGCUR_1 possible on PQ STAR query with PARTITIONED fact table
Fixed: 8.1.6.3, 8.1.7.0

Bug# 1297674 See Note 1297674.8
OERI:25012 Analyzing partitioned table with ESTIMATE
Fixed: 8.0.6.2, 8.1.6.3, 8.1.7.0

Bug# 1264970 See Note 1264970.8
OERI:25012 / OERI:6050 possible coalescing index with freelists
Fixed: 8.1.7.1, 9.0.1.0

Bug# 1228658 See Note 1228658.8
Create INDEX on SNAPSHOT/MV can produce corrupt index (OERI:13004 / OERI:25012 / ORA-1499)
Fixed: 8.1.6.2, 8.1.7.0

Bug# 1138239 See Note 1138239.8
OERI-25012 possible on direct read from plugged in (transportable) tablespace
Fixed: 8.1.6.2, 8.1.7.0

Bug# 1108002 See Note 1108002.8
OERI:25012 when DBMS_STATS tries to gather stats for a GLOBAL TEMPORARY table
Fixed: 8.1.7.0

Bug# 986928 See Note 986928.8
DBMS_SPACE.UNUSED_SPACE reports OERI:25012 for TEMPORARY tables
Fixed: 8.1.7.0

Bug# 718499 See Note 718499.8
OERI:25012 possible on OPS parallel create index
Fixed: 8.0.6.1, 8.1.5.0

Bug# 679817 See Note 679817.8
OERI:25012 from view containing 2+ LOB columns
Fixed: 8.0.5.1

Bug# 677243 See Note 677243.8
OERI:kdddgbX on DELETE / UPDATE / SELECT for UPDATE with an invalid ROWID
Fixed: 8.0.6.0

Bug# 595698 See Note 595698.8
DELETE on table with many child constraints may dump.
Fixed: 8.0.4.3, 8.0.5.0

<Internal_Only>

If this is an INSERT operation then consider the use of diagnostic
EVENT 10364.

This is available from Oracle 8.1.7.4 onwards (from Bug 2195129). If
this error is encountered during INSERTs, then the error can be suppressed.
Under these conditions, additional diagnostic information is written to the
trace file. (see the event note for more details)

ORA-600 [25012] [a] [b] [] [] []
Versions: 8.0 Source: kft.c

===========================================================================
Meaning:

<Function:kftr2ah> Relative to absolute file number translation with
hint. 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 it is zero. The ?hint? is the absolute file number,
available to the cache layer only. It is stored in the buffer descriptor.

---------------------------------------------------------------------------
Argument Description:

a. Tablespace Number.
b. Relative file number.

---------------------------------------------------------------------------
Diagnosis:

1. Get the trace file.

2. Find out what the current SQL statement is. Check for
ANALYZE/DBMS_SPACE.

3. Get the definition of the object. Is it an index-organized table?
Is it partitioned?

Note that this can occur if the dictionary is corrupt. To check for
greater than four million block problems see Note 107591.1.

---------------------------------------------------------------------------
Articles:

Note 107591.1 Checking for more than 4 million blocks on a file

---------------------------------------------------------------------------
Known Bugs:

There are many bugs logged against this - mostly areas 2 and 3 above
(under Diagnosis). There are too many to list.

Ensure that this note comes out on top in Metalink when searched
ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600
ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600
25012 25012 25012 25012 25012 25012 25012 25012 25012 25012
25012 25012 25012 25012 25012 25012 25012 25012 25012 25012

</Internal_Only>

C'est quelle version exactement d'Oracle ?

**orafrance** · 15/04/2005, 16h39

Essaye ça :

PURPOSE
-------
To fix error ORA-00600 [25012], while performing select or insert on a table.
SCOPE & APPLICATION
-------------------
All users.
ORA-00600 [25012], while performing select or insert on a table
---------------------------------------------------------------
Description:
------------
You are always getting error, ORA-00600 [25012], while doing select or
insert on a table.
The table has indexes created with PARALLEL clause.
Cause:
------
Bug 2531519 <ml2_documents.showDocument?p_id=2531519&p_database_id=BUG>
Loading data into a bitmap managed table using parallel direct-path insert may
fail with ORA-600 [25012] errors.
Solution:
---------
Recreate the indexes with NOPARALLEL clause.
The bug is fixed in 9203 release. One off patches are available on 9202 and 9.0.1.X
releases.

Ou ça :

Symptom(s)
~~~~~~~~~~
ORA-600 [25012] errors with same first argument and different
second arguments (second arguments changes during every SELECT Run)
Eg.:
ORA-600 [25012], [5], [1023], [], [], [], []
The first argument corresponds to a tablespace and second argument
corresponds to a file number.
The tablespace points to an index tablespace
Cause
~~~~~
[BUG:2184731] <ml2_documents.showDocument?p_id=2184731&p_database_id=BUG>
Fix
~~~~
[BUG:2184731] <ml2_documents.showDocument?p_id=2184731&p_database_id=BUG> is fixed in 8.1.7.4 and 9.2
The workaround is to set _db_file_noncontig_mblock_read_count=1.