support.oracle.com epmos faces documentdisplay afrloop

OERR: ORA-8103 "object no longer exists" Master Note / Troubleshooting,

Diagnostic and Solution (Doc ID 8103.1)

Modified: 15-Oct-2013 Type: REFERENCE

In this Document

Purpose

Scope

Details

Description

Cause

Expected behavior.

Block Corruption.

Overlapped Extents.

Overlapped ASM extent.

Oracle defect.

Identify the affected object

Get the SQL statement that is causing the error.

Identify the affected object with ANALYZE.

Identify the object with event 10236.


Identify object affected by Block Corruption.

Identify object affected by Overlapped Extents.

Using the call stack trace arguments to identify the block producing the ORA-8103.

Solution

Fix Block Corruption.

Flush the buffer cache.

Index Corruption.

Table Corruption.

OPTION 1 - No backup


Temporary Segment Corruption

Fix Overlapped Extents.

References

APPLIES TO:

Oracle Database - Enterprise Edition - Version 8.1.5.0 to 11.2.0.3 [Release 8.1.5 to 11.2]Information in this document applies to any platform.

PURPOSE

This article provides information about error ORA-8103 and possible actions.

of 12Document 8103.1

17/12/34https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=enhk5u4ed_9...

SCOPE

This note is intended for general audience as initial starting point for beginning diagnosis of ORA-8103.

DETAILS

Error: ORA 8103

Text: object no longer exists

-------------------------------------------------------------------------------

Cause: The object has been deleted by another user since the operation began.

Action: Remove references to the object.

Description

ORA-8103 is reporting that a SQL statement found a block that no longer belongs to the object referenced in the statement.

Cause

ORA-8103 is caused by an invalid block type. The block header has an invalid block type or the block type inside the block is not expected; e.g. a data block (Type=6) was expected but the actual block information is not a data block (Type!=6).

ORA-8103 is also caused by an unexpected data_object_id where it is changing for the involved objects while the affected SQL statement is executed.

These two causes might be due to an expected behavior or other problems. Details are:

Expected behavior.

Tables are being dropped/truncated while a SQL statement for those tables is still in execution. In the case of an index, it might be caused by an index rebuild. In other words the object has been deleted by another session since the operation began.

Look if dba_objects.data_object_id is changing for the affected object while queries are being executed.

data_object_id is changed by DDL statements like:

truncate table

alter index .. rebuild

alter table .. move

etc.

For a truncate look for column TRUNCATED in DBA_TAB_MODIFICATIONS. Note that it indicates whether the table has been truncated since the last analyze. See documentation.

In 11g parameter enable_ddl_logging can be set to TRUE to print DDL statements in the alert log and identify what DDL's are run that may potentially cause this error.

Block Corruption.



Hardware, IO subsystem or OS problems may cause block corruptions overwriting the Block Type in the block header causing the error ORA-8103.

The block is healthy but it is an "OLD/STALE" block. These kind of corruptions might be caused by LOST IO/LOST WRITE or a bug in external non-oracle tools that migrate file systems while the database is OPEN. In that case the data_object_id for the affected object could have changed but the actual block does not reflect it.

Note that the block may also be temporarily corrupted in the buffer cache (SGA Memory).

Overlapped Extents.

Overlapped Extents means that two or more segments incorrectly use the same block. This is a LMT Bitmap Extent inconsistency or Data Dictionary inconsistency.

To identify overlapped extents run the next checks:

For LMT (Locally Managed Tablespaces) run :

sqlplus / as sysdba

execute dbms_space_admin.tablespace_verify('&tablespace_name')oradebug setmypidoradebug tracefile_name

In 10gR2 and forward, for locally managed tablespaces using ASSM (DBA_TABLESPACES.SEGMENT_SPACE_MANAGEMENT=AUTO) run:

execute dbms_space_admin.assm_tablespace_verify('&tablespace_name',dbms_space_admin.TS_VERIFY_BITMAPS)oradebug setmypidoradebug tracefile_name

• Note that the session running dbms_space_admin does not say in the screen if an

inconsistency is detected. dbms_space_admin will generate a trace file instead. So check if "oradebug tracefile_name" provides a trace file.

• If ORA-8103 is produced by tablespace_verify, it means that a block associated to the segment header is affected. Identify the affected object as explained in the section below and drop it. It may convert the segment to temporary which may need the usage of dbms_space_admin.segment_corrupt and dbms_space_admin.segment_drop to completely remove the segment.

For Data Dictionary managed tablespaces run the hcheck script in:

Note 136697.1 (it checks for overlapped extents through fet$/uet$).

Overlapped ASM extent.

If using ASM: overlapped ASM extents is when 2 different files and 2 different extents use the same Allocation Unit (AU) in the same ASM disk.

From the ASM instance run:

SQL> alter diskgroup <name> check all norepair;



In ASM alert log the next message is registered:

ERROR: file +data1.3551.721223631: F3551 PX3819 => D254 A78 => F3564

PX337: fnum mismatch

Meaning that ASM file number 3551 Physical Extent 3819 is using Allocation unit 78 in Disk 254 and at the same time ASM File Number 3564 has Physical Extent pointing to the same Allocation unit.

Oracle defect.

It can be an Oracle bug. See section "known issues" below.

Identify the affected object

Sometimes the SQL statement producing the ORA-8103 involves several tables and the affected object can be an index. Follow the next procedures to identify the affected object:

Get the SQL statement that is causing the error.

Reproduce the error from SQL*Plus if possible by running the affected SQL statement.

Identify the affected object with ANALYZE.

Is it a TABLE or an INDEX causing the error?:

For a TABLE run:

analyze table <table_name> validate structure;

Alternatively identify if a full table scan is producing the error.

For an INDEX run:

analyze index <index_name> validate structure;


In 9.2.0.8 or above if ktrget is in the call stack trace for an ORA-8103, setting Event 10236 will include the block number causing the error:

alter session set events '8103 trace name errorstack level 3';

alter session set events '10236 trace name context forever, level 1';alter session set tracefile_identifier='ORA8103';

run the query that produces the error ORA-8103 and identify the trace

with the form of <sid>_ora_<pid>_ORA8103.trc

Open the trace file and if function ktrget is in the call stack trace, then the trace file may have:

KTRVAC: path typ=22, rdba=32810e06



Meaning that the error is produced in rdba=0x32810e06 . Convert that number to decimal and

get the relative_fno, block#:

select dbms_utility.data_block_address_file(847318534) relative_fno

,dbms_utility.data_block_address_block(847318534) block#from dual;

RELATIVE_FNO BLOCK#------------ ----------

202 69126

Then use Note <> to identify the object; section "Identify the Corrupt Object".


Event 10200 can be used to identify the last accessed block when this error is produced. event trace_buffer_on can be used to generate a smaller trace file. Errorstack and event 10236 can be added to get a more complete trace file:

alter session set max_dump_file_size=unlimited;

alter session set db_file_multiblock_read_count=1;alter session set events 'immediate trace name trace_buffer_on level

1048576';alter session set events '10200 trace name context forever, level 1';

alter session set events '8103 trace name errorstack level 3';

alter session set events '10236 trace name context forever, level 1';alter session set tracefile_identifier='ORA8103';

run the query that produces the error ORA-8103

alter session set events 'immediate trace name trace_buffer_off';exit

Identify the trace with the form of <sid>_ora_<pid>_ORA8103.trc

In the trace file generated locate last information about:

"Consistent read started for block <XXX>: <YYY>"

where XXX is the tablespace number and YYY is the rdba for that block. Normally this is the affected block.

Trace output example:

*** 2004-01-28 09:40:16.000*** SESSION ID:(9.5) 2004-01-28 09:40:16.000Consistent read started for block 0 : 00405302

env: (scn: 0x0000.001a9434 xid: 0x0000.000.00000000 uba: 0x00000000.0000.00 statement num=0 parent xid: xid: 0x0000.000.00000000

scn: 0x0000.00000000 0sch: scn: 0x0000.00000000)CR exa ret 9 on: 01FEE950 scn: 0xffff.ffffffff xid: 0x0000.000.00000000 uba: 0x00000000.0000.00 scn: 0xffff.ffffffff sfl: 0

Consistent read finished for block 0 : 405302Consistent read finished for block 0 : 405302

Consistent read started for block 0 : 00405303

The error is produced while reading rdba=0x00405303 (File=1,Block=21251) as there is NOT a message like:"Consistent read finished for block 0 : 00405303"



Then use Note <> to identify the object; section "Identify the Corrupt Object".

Identify object affected by Block Corruption.

Use DBVerify or RMAN to identify corrupted blocks associated to the datafiles where the object is stored.

A common corruption is when the block has been zeroed out (block type is also zero). DBVerify reports it as:

Completely zero block found during dbv

Use sections "DBVerify - Identify Datafile Block Corruptions" or "RMAN - Identify Datafile Block Corruptions" in Note 836658.1 and Note 819533.1 to identify the affected object.

Identify object affected by Overlapped Extents.

If overlapped extents in Locally Managed Tablespace is identified, use Note 887263.1 to identify the segments involved.

Solution

Fix Block Corruption.

If error ORA-8103 is constantly reproduced by ANALYZE and if it has been determined that it is not the expected behavior, then it means that there is a possible block corruption. The possible solutions are:

Flush the buffer cache.

It might be a corruption only in the SGA memory (Buffer cache):

alter session set events 'immediate trace name flush_cache

level 1';

In a RAC system, flushing the buffer cache may be needed in the additional rac instances.

If error still persists it means the the block is invalid also in disk, so continue with the next steps:

Index Corruption.

Drop and recreate the index.

Table Corruption.



1. Consider to apply media recovery if it is determined that the problem was caused by a corrupt block (Like zeroed out blocks). RMAN BLOCKRECOVER can

be used to repair a zeroed out block.

2. TRUNCATE or DROP it and reload the data from export dump. If the the same error is produced by dropping/truncating a PARTITION, then consider to EXCHANGE:

alter table <owner>.<table_name> exchange partition <partition_name> with table <owner>.<new_table>;

Note: <new_table> has to have the same structure as <table_name>.

3. If recover from a backup is not an option, table data can be saved skipping the blocks that are causing the ORA-8103 error:


If the table has an index use the plsql script provided in Note 1527738.1


If the table does not have an index, use script provided in Note 422547.1

Another solution is to determine if dbms_repair can be used to skip these blocks or if procedure described in Note 61685.1 can be used to skip corrupted blocks using rowid scans.

Temporary Segment Corruption

If it is identified that the ORA-8103 is caused by a temporary segment, use

dbms_space_admin to drop the temporary segment and rebuild the tablespace bitmap:

sqlplus / as sysdba

execute dbms_space_admin.segment_corrupt('&tablespace_name',&relative_fno,&block_number)execute dbms_space_admin.segment_drop_corrupt('&tablespace_name',&relative_fno,&block_number)execute dbms_space_admin.tablespace_rebuild_bitmaps('&tablespace_name')

Fix Overlapped Extents.

If the error is caused by Overlapped extents in a LOCALLY MANAGED Tablespace (LMT):

• Drop one of the affected objects. If the segment is converted to temporary then use dbms_space_admin.segment_corrupt and dbms_space_admin.segment_drop to remove the segment.

• Make sure that there are not more overlap extents by running dbms_space_admin.assm_tablespace_verify or dbms_space_admin.tablespace_verify



• Fix the overlap inconsistency by running dbms_space_admin.tablespace_rebuild_bitmaps. Note that it will not fix the current

affected blocks producing ORA-8103.

For a DICTIONARY MANAGED tablespace determine if the database has to be recreated.

Known Bugs

You can restrict the list below to issues likely to affect one of the following versions by clicking the relevant button:

9.2.0.8 10.1.0.5 10.2.0.2 10.2.0.3 10.2.0.4 10.2.0.5 11.1.0.6 11.1.0.7

11.2.0.1 11.2.0.2 11.2.0.3 12.1.0.1 Show all Bugs

NB Bug Fixed Description

15996357 12.2.0.0 ORA-8103 when revoking DBA privileges

13785734 11.2.0.4, 12.2.0.0ORA-8103 or similar from queries on partitioned table in standby

1391042011.2.0.3.6, 11.2.0.3.BP09,

11.2.0.4, 12.1.0.1

ORA-8103 during insert / update of basicfile LOB

in assm segment using space search cache

1372539511.2.0.3.8, 11.2.0.3.BP07, 11.2.0.4, 12.1.0.1

ORA-600 [kdzhFindHeadPiece: unnewed > 1] from load into HCC table

1370057711.2.0.3.BP07, 11.2.0.4, 12.1.0.1

PQ slave dies with ORA-600 [kdblddr_2]

1274743711.2.0.3.8, 11.2.0.3.BP21, 11.2.0.4, 12.1.0.1

ORA-600 [ktspfmdb:objdchk_kcbnew_3] after purging single consumer queue table

12582839 11.2.0.3, 12.1.0.1ORA-8103/ORA-600 [3020] on RMAN recovered locally managed tablespace

P 12330911 12.1.0.1 EXADATA LSI firmware for lost writes

12321309 11.2.0.4, 12.1.0.1ORA-600 / ORA-8103 UNUSABLE state of partitioned index is not carried across by

TABLESPACE transport using DataPump

1193725311.2.0.2.6, 11.2.0.2.BP11, 11.2.0.3, 12.1.0.1

A Parallel query fails with ORA-8103 on an Active Dataguard Enviroment.

11850492 11.2.0.3, 12.1.0.1ORA-8103 ORA-600 ORA-3113 on temporary tables using INDEX FAST FULL SCAN and DIRECT read

1038581211.2.0.2.BP20, 11.2.0.3, 12.1.0.1

ORA-1410 or ORA-8103 by queries with DIRECT READ while concurrent DIRECT INSERT

10329146

11.2.0.1.BP10, 11.2.0.2.2, 11.2.0.2.BP03, 11.2.0.2.GIBUNDLE02, 11.2.0.2.GIPSU02,

11.2.0.3, 12.1.0.1

Lost write in ASM with multiple DBWs and a disk is offlined and then onlined

+ 10209232

11.1.0.7.7, 11.2.0.1.BP08, 11.2.0.2.1, 11.2.0.2.BP02, 11.2.0.2.GIBUNDLE01, 11.2.0.3, 12.1.0.1

ORA-1578 / ORA-600 [3020] Corruption. Misplaced Blocks and Lost Write in ASM

10136415 11.2.0.3, 12.1.0.1ORA-8103 on Partitioned IOT after partition maintenance

9965085 11.2.0.3, 12.1.0.1



ORA-1578 / ORA-8103 Temporary table block corruption / space wastage from PDML -

superseded

965961410.2.0.5.3, 11.2.0.3.5, 11.2.0.3.BP05, 11.2.0.4, 12.1.0.1

Large trace file for ORA-8103

965135011.2.0.2.2, 11.2.0.2.BP05, 11.2.0.3, 12.1.0.1

Large redo dump and ORA-308 might be raised due to ORA-8103

9275027 11.2.0.2, 12.1.0.1ORA-600 [kcbnew_3] can occur after TRUNCATE / DROP

927208611.1.0.7.4, 11.2.0.1.2, 11.2.0.1.BP06, 11.2.0.2, 12.1.0.1

ORA-8103 by a query on DBA_EXTENTS. Trace file with Block type: 0x44=NGLOB: Extent Map

8754670 11.2.0.2, 12.1.0.1IMP-17 / ORA-8103 transporting a large

dictionary managed tablespace

874099311.1.0.7.8, 11.2.0.2, 12.1.0.1

ORA-1410 / ORA-8103 on ADG STANDBY during table scan after DROP/TRUNCATE/SHRINK in PRIMARY

872528211.2.0.1.BP08, 11.2.0.2, 12.1.0.1

Corruption from cross platform transport of tablespace with securefile objects

8716064 11.2.0.2, 12.1.0.1Analyze Table Validate Structure fails on ADG standby with several errors

+ 859710611.2.0.1.BP06, 11.2.0.2, 12.1.0.1

Lost Write in ASM when normal redundancy is used

8428523 11.2.0.2, 12.1.0.1Alter Table Rename causes wrong results/ora-8103/hangs on ADG Standby.

7710827 11.2.0.2, 12.1.0.1Index rebuild or Merge partition causes wrong

results in concurrent reads instead of ORA-8103

751940610.2.0.5.1, 11.2.0.1.2, 11.2.0.1.BP06, 11.2.0.2, 12.1.0.1

Larger trace than needed for ORA-8103 under kteinicnt1

8876094 11.1.0.7.2, 11.2.0.2ORA-8103 by DBA_UNDO_EXTENTS or DBMS_SPACE_ADMIN.TABLESPACE_VERIFY on Block type: 0x25

9167831 11.2.0.2 ORA-8103 instead of ORA-1410

7650993 11.1.0.7.1, 11.2.0.1ORA-8103 in a select at ADG standby database from table stored in ASSM tablespace

7432556 11.1.0.7.1, 11.2.0.1ORA-8103 by Parallel Query on Partitioned Tables in BIGFILE Tablespaces

7390324 11.2.0.1ANALYZE signals OERI [kcbgtcr_12]/ORA-8103 on bitmap index

7117200 11.2.0.1ORA-8103 after TSPITR/PLUGIN tablespace from a restored Level 1 Backup

8825048 11.1.0.7.3ORA-308/ORA-27037 when dumping archived log for ORA-8103. Dump when event 10736 level 4 is set

6337376 11.1.0.7OERI:kcbgcur_3 / ORA-8103 after truncating a partition table with LOBs

9711472 11.1.0.6ORA-8103 on operations for a partitioned LOB if any different partition is dropped

5637976 10.2.0.4, 11.1.0.6ORA-8103/ORA-1410 from concurrent INSERT /

export on ASSM tables



5083393 10.2.0.4, 11.1.0.6 DBA_FREE_SPACE FILE_ID / REL_FNO may be wrong

4592596 10.2.0.4, 11.1.0.6Corruption (ORA-1410 / ORA-8103) from multi-

table insert with direct load

6864586 10.2.0.5ORA-8103 on partitioned table with a LOB column during analyze table with concurrent add/drop partition.

3569503 9.2.0.6, 10.2.0.4 PQ may signal a false ORA-8103 under load

13618170ORA-8103 for create index online when the fix of bug 10027403 is installed

3966709 9.2.0.7, 10.1.0.4, 10.2.0.1 Range/object reuse prematurely (ORA-8103)

3868753 9.2.0.7, 10.1.0.5, 10.2.0.1Concurrent export / INSERT of ASSM segment can fail with ORA-1410 / ORA-8103

+ 5523799Various OERI (eg kcbgtcr_12) using ASSM managed segments - superceded

P* 6047085Linux x64-64: SGA corruption / crash following any ORA-7445

* 3785200 9.2.0.6, 10.1.0.2Corruption possible in automatic space managed segments

3083560 9.2.0.5, 10.1.0.2ORA-1410 / ORA-8103 from direct path export if concurrent DML occurs

2619867 9.2.0.3, 10.1.0.2OERI:[KCBGTCR_12] / ORA-8103 / ORA-1410 SELECTing from bitmap managed segment

2551000 10.1.0.2, 9.2.0.4False ORA-1410 / ORA-8103 possible from ANALYZE COMPUTE/ESTIMATE STATISTICS

2333731 9.2.0.2 ORA-8103 possible in PQ slave

2105419 9.0.1.3, 9.2.0.1ORA-8103 possible from PQ on bitmap managed

segments with concurrent inserts

1998455 8.1.7.3, 9.0.1.3, 9.2.0.1OERI:KCBGTCR_4 possible from long running DDL if referenced object dropped/truncated

1804299 9.0.1.1, 9.2.0.1Rollback of Direct load can corrupt BITMAP managed segments / ORA-8103

1698789 9.2.0.1Wrong results, ORA-1410, ORA-8103, OERI:25012 on SELECT of UNSCOPED REF with ROWID

1504967 9.2.0.1ORA-8103 possible on READ ONLY standby after TRUNCATE on primary

1400739 8.1.7.1, 9.0.1.0Block corruption/OERI:2023 /ORA-8103 can occur if TRUNCATE is interrupted (Ctrl-C)

1283521 8.1.7.0ORA-8103 can occur on TRUNCATED cluster

table

589855 7.3.3.6, 7.3.4.1 ORA:1578 or ORA:8103 selecting invalid ROWID

P 1053863 8.0.5.2, 8.0.6.2NCR: ORA-8103 / corrupt read possible using async IO

• '*' indicates that an alert exists for that issue.• '+' indicates a particularly notable issue / bug.• 'P' indicates a port specific bug.• "OERI:xxxx" may be used as shorthand for ORA-600 [xxxx].



REFERENCES

NOTE:1504967.8 - Bug 1504967 - ORA-8103 possible on READ ONLY standby after TRUNCATE on primaryNOTE:136697.1 - "hcheck.sql" script to check for known problems in Oracle8i, Oracle9i, Oracle10g and

Oracle 11gNOTE:9272086.8 - Bug 9272086 - ORA-8103 by a query on DBA_EXTENTS. Trace file with Block type: 0x44=NGLOB: Extent MapNOTE:1698789.8 - Bug 1698789 - Wrong results, ORA-1410, ORA-8103, OERI:25012 on SELECT of UNSCOPED REF with ROWIDNOTE:2105419.8 - Bug 2105419 - ORA-8103 possible from PQ on bitmap managed segments with concurrent insertsNOTE:1804299.8 - Bug 1804299 - Rollback of Direct load can corrupt BITMAP managed segments / ORA-8103NOTE:3868753.8 - Bug 3868753 - Concurrent export / INSERT of ASSM segment can fail with ORA-1410 / ORA-8103NOTE:12582839.8 - Bug 12582839 - ORA-8103/ORA-600 [3020] on RMAN recovered locally managed

tablespaceNOTE:5523799.8 - Bug 5523799 - Various OERI (eg kcbgtcr_12) using ASSM managed segments -supercededNOTE:8716064.8 - Bug 8716064 - Analyze Table Validate Structure fails on ADG standby with several errorsNOTE:9651350.8 - Bug 9651350 - Large redo dump and ORA-308 might be raised due to ORA-8103NOTE:5083393.8 - Bug 5083393 - DBA_FREE_SPACE FILE_ID / REL_FNO may be wrongNOTE:7117200.8 - Bug 7117200 - ORA-8103 after TSPITR/PLUGIN tablespace from a restored Level 1 BackupNOTE:7390324.8 - Bug 7390324 - ANALYZE signals OERI [kcbgtcr_12]/ORA-8103 on bitmap indexNOTE:3083560.8 - Bug 3083560 - ORA-1410 / ORA-8103 from direct path export if concurrent DML occursNOTE:3569503.8 - Bug 3569503 - PQ may signal a false ORA-8103 under load

NOTE:1400739.8 - Bug 1400739 - Block corruption/OERI:2023 /ORA-8103 can occur if TRUNCATE is interrupted (Ctrl-C)NOTE:7432556.8 - Bug 7432556 - ORA-8103 by Parallel Query on Partitioned Tables in BIGFILE TablespacesNOTE:2619867.8 - Bug 2619867 - OERI:[KCBGTCR_12] / ORA-8103 / ORA-1410 SELECTing from bitmap managed segmentNOTE:7710827.8 - Bug 7710827 - Index rebuild or Merge partition causes wrong results in concurrent reads instead of ORA-8103NOTE:819533.1 - How to identify the corrupt Object reported by ORA-1578 / RMAN / DBVERIFYNOTE:1998455.8 - Bug 1998455 - OERI:KCBGTCR_4 possible from long running DDL if referenced object dropped/truncated

NOTE:4592596.8 - Bug 4592596 - Corruption (ORA-1410 / ORA-8103) from multi-table insert with direct loadNOTE:3966709.8 - Bug 3966709 - Range/object reuse prematurely (ORA-8103)NOTE:8428523.8 - Bug 8428523 - Alter Table Rename causes wrong results/ora-8103/hangs on ADG Standby.NOTE:9965085.8 - Bug 9965085 - ORA-1578 / ORA-8103 Temporary table block corruption / space wastage from PDMLNOTE:887263.1 - How to identify the SEGMENT reported by dbms_space_admin.TABLESPACE_VERIFYNOTE:6864586.8 - Bug 6864586 - ORA-8103 on partitioned table with a LOB column during analyze table with concurrent add/drop partition.NOTE:12747437.8 - Bug 12747437 - ORA-600 [ktspfmdb:objdchk_kcbnew_3] after purging single consumer

queue tableNOTE:589855.8 - Bug 589855 - ORA:1578 or ORA:8103 selecting invalid ROWIDNOTE:8740993.8 - Bug 8740993 - ORA-1410 / ORA-8103 on ADG STANDBY during table scan after DROP/TRUNCATE/SHRINK in PRIMARYNOTE:8825048.8 - Bug 8825048 - ORA-308/ORA-27037 when dumping archived log for ORA-8103. Dump when event 10736 level 4 is setNOTE:8754670.8 - Bug 8754670 - IMP-17 / ORA-8103 transporting a large dictionary managed tablespaceNOTE:422547.1 - Extract rows from a CORRUPT table creating ROWID from DBA_EXTENTSNOTE:9659614.8 - Bug 9659614 - Large trace file for ORA-8103NOTE:10329146.8 - Bug 10329146 - Lost write in ASM with multiple DBWs and a disk is offlined and then onlined



NOTE:10385812.8 - Bug 10385812 - ORA-1410 or ORA-8103 by queries with DIRECT READ while concurrent DIRECT INSERT

NOTE:9711472.8 - Bug 9711472 - ORA-8103 on operations for a partitioned LOB if any different partition is droppedNOTE:10136415.8 - Bug 10136415 - ORA-8103 on Partitioned IOT after partition maintenanceNOTE:10209232.8 - Bug 10209232 - ORA-1578 / ORA-600 [3020] Corruption. Misplaced Blocks and Lost Write in ASMNOTE:9167831.8 - Bug 9167831 - ORA-8103 instead of ORA-1410NOTE:7519406.8 - Bug 7519406 - Larger trace than needed for ORA-8103 under kteinicnt1NOTE:7650993.8 - Bug 7650993 - ORA-8103 in a select at ADG standby database from table stored in ASSM tablespaceNOTE:2333731.8 - Bug 2333731 - ORA-8103 possible in PQ slaveNOTE:2551000.8 - Bug 2551000 - False ORA-1410 / ORA-8103 possible from ANALYZE

COMPUTE/ESTIMATE STATISTICSNOTE:8876094.8 - Bug 8876094 - ORA-8103 by DBA_UNDO_EXTENTS or DBMS_SPACE_ADMIN.TABLESPACE_VERIFY on Block type: 0x25NOTE:1053863.8 - Bug 1053863 - NCR: ORA-8103 / corrupt read possible using async IONOTE:6047085.8 - Bug 6047085 - Linux x64-64: SGA corruption / crash following any ORA-7445NOTE:1283521.8 - Bug 1283521 - ORA-8103 can occur on TRUNCATED cluster tableNOTE:836658.1 - Identify the corruption extension using RMAN/DBV/ANALYZE etcNOTE:5637976.8 - Bug 5637976 - ORA-8103/ORA-1410 from concurrent INSERT / export on ASSM tablesNOTE:61685.1 - Extracting Data from a Corrupt Table using ROWID Range Scans in Oracle8 and higher

NOTE:8597106.8 - Bug 8597106 - Lost Write in ASM when normal redundancy is usedNOTE:9275027.8 - Bug 9275027 - ORA-600 [kcbnew_3] can occur after TRUNCATE / DROP

NOTE:8725282.8 - Bug 8725282 - Corruption from cross platform transport of tablespace with securefile objectsNOTE:11850492.8 - Bug 11850492 - ORA-8103 ORA-600 ORA-3113 on temporary tables using INDEX FAST FULL SCAN and DIRECT readNOTE:11937253.8 - Bug 11937253 - A Parallel query fails with ORA-8103 on an Active Dataguard Enviroment.NOTE:3785200.8 - Bug 3785200 - Corruption possible in automatic space managed segmentsNOTE:1527738.1 - SCRIPT to skip ORA-8103 ORA-1410 ORA-1578 ORA-600 [kdsgrp1] when reading a TABLE



support.oracle.com epmos faces documentdisplay afrloop

Documents