Pular para o conteúdo

Fóruns Banco de dados Oracle Removendo um índice teimoso… Removendo um índice teimoso…

#85606
Rodrigo Almeida
Participante

    Subject: ORA-600 [25012] “Relative to Absolute File Number Conversion Error”
    Doc ID: 100073.1 Type: REFERENCE
    Modified Date : 24-FEB-2009 Status: PUBLISHED

    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.

    If the Arg [b] Relative file number returns 0 (zero), look for fake indexes
    that can cause this error.

    The following query list fake indexes :

    select a.*,b.flags from dba_objects a, sys.ind$ b
    where a.object_id = b.obj#
    and bitand(b.flags,4096)=4096;

    Known Issues:

    Bug# 5653641 See Note 5653641.8
    Corrupt dictionary from DROP TABLESPACE containing _offline_rollback_segments
    Fixed: 11.2

    Bug# 4925342 See Note 4925342.8
    OERI [25027] / OERI [25012] on IOT analyze estimate statistics
    Fixed: 9.2.0.8, 10.2.0.3, 11.1.0.6

    Bug# 4305391 See Note 4305391.8
    OERI[25012] with kditalp can occur during a temporary LOB operation
    Fixed: 9.2.0.7, 10.1.0.5, 10.2.0.1

    Bug# 3915343 See Note 3915343.8
    OERI [25012] on COMMIT with refresh ON-COMMIT Materialized view over cluster
    Fixed: 9.2.0.7, 10.1.0.5, 10.2.0.1

    Bug# 3900237 See Note 3900237.8
    OERI[25012] changing length of indexed column for a global temporary table
    Fixed: 9.2.0.7

    Bug# 3771508 See Note 3771508.8
    OERI[kcbgtcr_1] / OERI[25012] selecting from V$AQ in a shared server
    Fixed: 9.2.0.7

    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.0.1

    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.0.1

    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.0.1

    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 indextable 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

    Marcio,

    Passa o patchset que está aplicado no banco de dados, se é 9.2.0.1, 9.2.0.2, 9.2.0.3 e etc…

    Sobre os índices com NOSEGMENTS, basta ver um arquivo de parâmetro da instância, o parâmetro _use_nosegment_indexes, é um parâmetro oculto.

    Sobre o primeiro parâmetro do seu erro ORA-600, no metalink deu isso:

    ================================================