Page 1 of 12
OERR: ORA-8103 "object no longer exists" Master Note / Troubleshooting,
Diagnostic and Solution (Doc ID 8103.1)
In this Document
Overlapped ASM extent.
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 the object with event 10200.
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.
Fix Block Corruption.
Flush the buffer cache.
OPTION 1 - No backup
OPTION 2 - No backup
Temporary Segment Corruption
Fix Overlapped Extents.
Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 8.1.5 to 11.2]
Information in this document applies to any platform.
This article provides information about error ORA-8103 and possible actions.
These two causes might be due to an expected behavior or other problems. Details are:
Expected behavior.com/epmos/faces/DocumentDisplay?_adf. a data block (Type=6) was expected but the actual block information
is not a data block (Type!=6).
Tables are being dropped/truncated while a SQL statement for those tables is still in
Block Corruption. See documentation..
ORA-8103 is caused by an invalid block type. In the case of an index.
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. e.
ORA-8103 is reporting that a SQL statement found a block that no longer belongs to the object referenced
in the statement.
data_object_id is changed by DDL statements like:
alter index .g.
Error: ORA 8103
Text: object no longer exists
------------------------------------------------------------------------------Cause: The object has been deleted by another user since the operation began. The block header has an invalid block type or the block type
inside the block is not expected.
Action: Remove references to the object. In other words the
object has been deleted by another session since the operation began. Note that it
indicates whether the table has been truncated since the last analyze..
For a truncate look for column TRUNCATED in DBA_TAB_MODIFICATIONS.oracle. it might be caused by an index rebuild.1
Page 2 of 12
This note is intended for general audience as initial starting point for beginning diagnosis of ORA-8103. rebuild
alter table .ctrl-state=enhk5u4ed_9.Document 8103..
Look if dba_objects..data_object_id is changing for the affected object while queries are being
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.
Identify the affected object as explained in the section
below and drop it. for locally managed tablespaces using ASSM
• If ORA-8103 is produced by tablespace_verify.
To identify overlapped extents run the next checks:
For LMT (Locally Managed Tablespaces) run :
sqlplus / as sysdba
execute dbms_space_admin. It may convert the segment to temporary which may need the
usage of dbms_space_admin.oracle. This is
a LMT Bitmap Extent inconsistency or Data Dictionary inconsistency.tablespace_verify('&tablespace_name')
In 10gR2 and forward.
The block is healthy but it is an "OLD/STALE" block.segment_corrupt and dbms_space_admin.com/epmos/faces/DocumentDisplay?_adf. So
check if "oradebug tracefile_name" provides a trace file.TS_VERIFY_BITMAPS)
• Note that the session running dbms_space_admin does not say in the screen if an
inconsistency is detected.dbms_space_admin. dbms_space_admin will generate a trace file instead.
For Data Dictionary managed tablespaces run the hcheck script in:
('&tablespace_name'.ctrl-state=enhk5u4ed_9. In that case the data_object_id for the affected object
could have changed but the actual block does not reflect it. it means that a block associated to the
segment header is affected.
From the ASM instance run:
SQL> alter diskgroup <name> check all norepair.
Overlapped Extents means that two or more segments incorrectly use the same block.
Note that the block may also be temporarily corrupted in the buffer cache (SGA Memory).1
Page 3 of 12
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.
Overlapped Extents..Document 8103.
execute dbms_space_admin.1 (it checks for overlapped extents through fet$/uet$).segment_drop
to completely remove the segment. 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.
Overlapped ASM extent. IO subsystem or OS problems may cause block corruptions overwriting the Block
Type in the block header causing the error ORA-8103..
alter session set events '10236 trace name context forever. level 1'.
alter session set tracefile_identifier='ORA8103'.com/epmos/faces/DocumentDisplay?_adf..
Identify the object with event 10236. See section "known issues" below.
Oracle defect. then the trace file may have:
KTRVAC: path typ=22.
run the query that produces the error ORA-8103 and identify the trace
with the form of <sid>_ora_<pid>_ORA8103.
Alternatively identify if a full table scan is producing the error.
It can be an Oracle bug. rdba=32810e06
Page 4 of 12
In ASM alert log the next message is registered:
ERROR: file +data1.Document 8103.
In 9. setting Event 10236 will
include the block number causing the error:
alter session set events '8103 trace name errorstack level 3'.oracle.
Identify the affected object with ANALYZE.8 or above if ktrget is in the call stack trace for an ORA-8103..trc
Open the trace file and if function ktrget is in the call stack trace.3551.ctrl-state=enhk5u4ed_9.0.
For an INDEX run:
analyze index <index_name> validate structure.
Is it a TABLE or an INDEX causing the error?:
For a TABLE run:
analyze table <table_name> validate structure.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
Identify the affected object
Sometimes the SQL statement producing the ORA-8103 involves several tables and the affected object can
be an index.
Reproduce the error from SQL*Plus if possible by running the affected SQL statement. Follow the next procedures to identify the affected object:
Get the SQL statement that is causing the error.
00 scn: 0xffff.
CR exa ret 9 on: 01FEE950 scn: 0xffff. Convert that number to decimal and
get the relative_fno.00 statement num=0 parent xid: xid: 0x0000.
. level 1'.000
Consistent read started for block 0 : 00405302
env: (scn: 0x0000.0000.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. section "Identify the Corrupt Object".
events '8103 trace name errorstack level 3'.
Identify the trace with the form of <sid>_ora_<pid>_ORA8103.00000000 0sch: scn: 0x0000.
Trace output example:
*** 2004-01-28 09:40:16.000.1
Page 5 of 12
Meaning that the error is produced in rdba=0x32810e06 .
Identify the object with event 10200.00000000 uba:
run the query that produces the error ORA-8103
alter session set events 'immediate trace name trace_buffer_off'.
set max_dump_file_size=unlimited.. block#:
select dbms_utility.001a9434 xid: 0x0000.---------202 69126
Then use Note <> to identify the object.00000000
uba: 0x00000000.ffffffff xid: 0x0000. event
trace_buffer_on can be used to generate a smaller trace file. level 1'.0000.oracle.000.000
*** SESSION ID:(9.Block=21251) as there is NOT
a message like:
"Consistent read finished for block 0 : 00405303"
Normally this is the affected block.dbms_utility. Errorstack and event 10236 can
be added to get a more complete trace file:
events '10236 trace name context forever.ffffffff sfl: 0
Consistent read finished for block 0 : 405302
Consistent read finished for block 0 : 405302
Consistent read started for block 0 : 00405303
The error is produced while reading rdba=0x00405303 (File=1.
set events 'immediate trace name trace_buffer_on level
events '10200 trace name context forever.5) 2004-01-28 09:40:16..Document 8103.ctrl-state=enhk5u4ed_9.data_block_address_block(847318534) block#
Event 10200 can be used to identify the last accessed block when this error is produced.000.
If error ORA-8103 is constantly reproduced by ANALYZE and if it has been determined that it
is not the expected behavior.
If overlapped extents in Locally Managed Tablespace is identified. section "Identify the Corrupt Object". then it means that there is a possible block corruption.Identify Datafile Block Corruptions" or "RMAN .1
Page 6 of 12
Then use Note <> to identify the object.Document 8103. The
possible solutions are:
Flush the buffer cache.
If error still persists it means the the block is invalid also in disk.
Use DBVerify or RMAN to identify corrupted blocks associated to the datafiles where the object
is stored.1 and Note 819533.
Fix Block Corruption.1 to
identify the segments involved.
Identify object affected by Block Corruption. so continue with
the next steps:
A common corruption is when the block has been zeroed out (block type is also zero). flushing the buffer cache may be needed in the additional rac
DBVerify reports it as:
Completely zero block found during dbv
Use sections "DBVerify .com/epmos/faces/DocumentDisplay?_adf.1 to identify the affected object. use Note 887263.
It might be a corruption only in the SGA memory (Buffer cache):
alter session set events 'immediate trace name flush_cache
Identify object affected by Overlapped Extents.ctrl-state=enhk5u4ed_9.oracle.Identify Datafile Block
Corruptions" in Note 836658..
Drop and recreate the index..
In a RAC system.
then consider to
alter table <owner>.No backup
If the table has an index use the plsql script provided in Note 1527738.1
Page 7 of 12
1. TRUNCATE or DROP it and reload the data from export dump.
• Make sure that there are not more overlap extents by running
Another solution is to determine if dbms_repair can be used to skip these blocks
or if procedure described in Note 61685.com/epmos/faces/DocumentDisplay?_adf.tablespace_rebuild_bitmaps
Fix Overlapped Extents.1
OPTION 2 . RMAN BLOCKRECOVER can
be used to repair a zeroed out block.. use
dbms_space_admin to drop the temporary segment and rebuild the tablespace
sqlplus / as sysdba
execute dbms_space_admin.assm_tablespace_verify or dbms_space_admin.
.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. If the the same
error is produced by dropping/truncating a PARTITION.<table_name> exchange partition
<partition_name> with table <owner>.No backup
If the table does not have an index.Document 8103.
If the error is caused by Overlapped extents in a LOCALLY MANAGED Tablespace (LMT):
• Drop one of the affected objects.ctrl-state=enhk5u4ed_9. If the segment is converted to temporary then use
('&tablespace_name'.segment_corrupt and dbms_space_admin.
Note: <new_table> has to have the same structure as <table_name>.&relative_fno.segment_corrupt
('&tablespace_name'. table data can be saved skipping
the blocks that are causing the ORA-8103 error:
OPTION 1 .tablespace_verify
https://support.&relative_fno.segment_drop to remove
the segment. use script provided in Note 422547.
execute dbms_space_admin. If recover from a backup is not an option.oracle. Consider to apply media recovery if it is determined that the problem was
caused by a corrupt block (Like zeroed out blocks).&block_number)
Page 8 of 12
• Fix the overlap inconsistency by running
EXADATA LSI firmware for lost writes
ORA-8103 or similar from queries on partitioned
table in standby
10.2. 12.0.2. 18.104.22.168
Lost write in ASM with multiple DBWs and a disk
is offlined and then onlined
For a DICTIONARY MANAGED tablespace determine if the database has to be recreated.0.2.1.1
ORA-600 [ktspfmdb:objdchk_kcbnew_3] after
purging single consumer queue table
12582839 11.4. 22.214.171.124
Show all Bugs
A Parallel query fails with ORA-8103 on an Active
Dataguard Enviroment.126.96.36.199.188.8.131.52.2.8. 184.108.40.206.1
10.2.2.0.2.Document 8103. Note that it will not fix the current
affected blocks producing ORA-8103.0.
You can restrict the list below to issues likely to affect one of the following versions by clicking
the relevant button:
11. 12.4. 220.127.116.11.2.2.2. 11. 11.
ORA-8103 when revoking DBA privileges
13785734 11. 11.1
ORA-8103/ORA-600  on RMAN recovered
locally managed tablespace
ORA-600 [kdzhFindHeadPiece: unnewed > 1]
from load into HCC table
ORA-1578 / ORA-600  Corruption.0.BP18.104.22.168.0.1.0.0.0.tablespace_rebuild_bitmaps.22.214.171.124.2
11.GIBUNDLE01.4.GIBUNDLE02.0.0.0.0.oracle.0.2.1. 12. 11.3.1
ORA-8103 on Partitioned IOT after partition
Misplaced Blocks and Lost Write in ASM
10136415 11. 11.1.2.BP02.
ORA-600 / ORA-8103 UNUSABLE state of
partitioned index is not carried across by
TABLESPACE transport using DataPump
11. 11.3.BP07.0.0. 11.2.0.BP126.96.36.199.1..2. 11.0. 12.
ORA-8103 ORA-600 ORA-3113 on temporary
tables using INDEX FAST FULL SCAN and
ORA-1410 or ORA-8103 by queries with DIRECT
READ while concurrent DIRECT INSERT
ORA-8103 during insert / update of basicfile LOB
in assm segment using space search cache
PQ slave dies with ORA-600 [kdblddr_2]
file with Block type: 0x44=NGLOB: Extent Map
ORA-308/ORA-27037 when dumping archived
log for ORA-8103.2.2.BP06.1.2. 188.8.131.52.1.0.
ORA-8103 by Parallel Query on Partitioned
Tables in BIGFILE Tablespaces
7390324 11.BP05. 11. 11.oracle.1
ORA-8103 after TSPITR/PLUGIN tablespace from
a restored Level 1 Backup
Analyze Table Validate Structure fails on ADG
standby with several errors
Lost Write in ASM when normal redundancy is
Large trace file for ORA-8103
Large redo dump and ORA-308 might be raised
due to ORA-8103
Index rebuild or Merge partition causes wrong
results in concurrent reads instead of ORA-8103
10.0.1.0.184.108.40.206.1.0. Dump when event 10736
level 4 is set
6337376 11.5. 11.0.1
ANALYZE signals OERI [kcbgtcr_12]/ORA-8103
on bitmap index
ORA-8103/ORA-1410 from concurrent INSERT /
export on ASSM tables
ORA-8103 in a select at ADG standby database
from table stored in ASSM tablespace
7432556 11. 11. 220.127.116.11. 18.104.22.168.3.1.
Alter Table Rename causes wrong results/ora8103/hangs on ADG Standby.2. 22.214.171.124.0.1
ORA-8103 by a query on DBA_EXTENTS.0.2. 12.0.BP05.1
IMP-17 / ORA-8103 transporting a large
dictionary managed tablespace
Corruption from cross platform transport of
tablespace with securefile objects
8716064 11. 12.0.
9272086 11.2.TABLESPACE_VERIFY on
Block type: 0x25
ORA-8103 on operations for a partitioned LOB if
any different partition is dropped
7710827 11.1.4. 126.96.36.199.2
ORA-8103 by DBA_UNDO_EXTENTS or
OERI:kcbgcur_3 / ORA-8103 after truncating a
partition table with LOBs
9711472 11.2.0. 11.2.0.
ORA-8103 instead of ORA-1410
7650993 11.BP06.5. 188.8.131.52.0.1
ORA-600 [kcbnew_3] can occur after
TRUNCATE / DROP
Page 9 of 12
ORA-1578 / ORA-8103 Temporary table block
corruption / space wastage from PDML superseded
184.108.40.206.220.127.116.11.18.104.22.168.ctrl-state=enhk5u4ed_9. 12. 11.1.1
ORA-1410 / ORA-8103 on ADG STANDBY during
table scan after DROP/TRUNCATE/SHRINK in
Larger trace than needed for ORA-8103 under
8876094 11.0.1. 12.BP08.
'P' indicates a port specific bug.0. 9. 10.0.7.0. 10.4
PQ may signal a false ORA-8103 under load
ORA-8103 for create index online when the fix of
bug 10027403 is installed
3966709 22.214.171.124.4. 9. 11.ctrl-state=enhk5u4ed_9. 10.2.3.0.1
Range/object reuse prematurely (ORA-8103)
3868753 9.0.7..1.0.7. 10.superceded
Linux x64-64: SGA corruption / crash following
DBA_FREE_SPACE FILE_ID / REL_FNO may be
3785200 126.96.36.199.0.0.1.0.2. 9.1.2
OERI:[KCBGTCR_12] / ORA-8103 / ORA-1410
SELECTing from bitmap managed segment
2551000 10.2.0.2. 188.8.131.52.0.5.6
ORA-1410 / ORA-8103 from direct path export if
concurrent DML occurs
Corruption (ORA-1410 / ORA-8103) from multitable insert with direct load
6864586 10.2.0. ORA-1410.0.
'+' indicates a particularly notable issue / bug.2
Corruption possible in automatic space managed
1053863 184.108.40.206. 11.
ORA-8103 possible on READ ONLY standby after
TRUNCATE on primary
Rollback of Direct load can corrupt BITMAP
managed segments / ORA-8103
1698789 9. 10.2.1
Concurrent export / INSERT of ASSM segment
can fail with ORA-1410 / ORA-8103
Various OERI (eg kcbgtcr_12) using ASSM
managed segments .2
ORA-8103 possible in PQ slave
2105419 9.2.0. 8.6.
False ORA-1410 / ORA-8103 possible from
ANALYZE COMPUTE/ESTIMATE STATISTICS
ORA-8103 can occur on TRUNCATED cluster
ORA:1578 or ORA:8103 selecting invalid ROWID
7. 9.1.2. 10.0.1
ORA-8103 possible from PQ on bitmap managed
segments with concurrent inserts
1998455 8. ORA-8103.
"OERI:xxxx" may be used as shorthand for ORA-600 [xxxx].0.0.6.com/epmos/faces/DocumentDisplay?_adf.3.1
OERI:KCBGTCR_4 possible from long running
DDL if referenced object dropped/truncated
ORA-8103 on partitioned table with a LOB
column during analyze table with concurrent
add/drop partition.0. 10.7.4. 7.2
NCR: ORA-8103 / corrupt read possible using
'*' indicates that an alert exists for that issue.1
Page 10 of 12
Block corruption/OERI:2023 /ORA-8103 can
occur if TRUNCATE is interrupted (Ctrl-C)
Wrong results.Document 8103..5.
OERI:25012 on SELECT of UNSCOPED REF with
1504967 9.0. 10. 9.
8 .Bug 8754670 .8 .Bug 2619867 .Bug 3083560 .8 .8 .8 .Block corruption/OERI:2023 /ORA-8103 can occur if TRUNCATE is
NOTE:9965085.ORA-8103/ORA-600  on RMAN recovered locally managed
NOTE:5523799.Bug 1998455 . Oracle10g and
NOTE:9272086.ANALYZE signals OERI [kcbgtcr_12]/ORA-8103 on bitmap index
NOTE:3083560.Bug 2105419 .Document 8103.8 ..Lost write in ASM with multiple DBWs and a disk is offlined and then
https://support.PQ may signal a false ORA-8103 under load
NOTE:1400739.8 .OERI:[KCBGTCR_12] / ORA-8103 / ORA-1410 SELECTing from bitmap
NOTE:7710827.ORA-308/ORA-27037 when dumping archived log for ORA-8103.DBA_FREE_SPACE FILE_ID / REL_FNO may be wrong
NOTE:7117200.ORA-1410 / ORA-8103 from direct path export if concurrent DML occurs
NOTE:3569503.com/epmos/faces/DocumentDisplay?_adf.8 .8 .Index rebuild or Merge partition causes wrong results in concurrent reads
instead of ORA-8103
NOTE:819533.ORA-1410 / ORA-8103 on ADG STANDBY during table scan after
DROP/TRUNCATE/SHRINK in PRIMARY
NOTE:8825048.Various OERI (eg kcbgtcr_12) using ASSM managed segments superceded
NOTE:8716064.Large redo dump and ORA-308 might be raised due to ORA-8103
NOTE:5083393.Corruption (ORA-1410 / ORA-8103) from multi-table insert with direct
.Bug 3569503 .1 .Bug 7432556 .Bug 8740993 .IMP-17 / ORA-8103 transporting a large dictionary managed tablespace
NOTE:422547.Bug 9659614 .1 .ORA-600 [ktspfmdb:objdchk_kcbnew_3] after purging single consumer
NOTE:589855. OERI:25012 on SELECT of
UNSCOPED REF with ROWID
NOTE:2105419.ORA-8103 after TSPITR/PLUGIN tablespace from a restored Level 1
NOTE:7390324.ORA-8103 on partitioned table with a LOB column during analyze table
with concurrent add/drop partition.8 . ORA-8103.8 .Bug 8716064 .8 .Bug 589855 .Bug 7117200 .oracle.8 .Bug 8825048 .8 .Analyze Table Validate Structure fails on ADG standby with several errors
NOTE:9651350.Bug 1698789 .8 .ORA-8103 by Parallel Query on Partitioned Tables in BIGFILE
NOTE:2619867.Bug 5083393 .Bug 12747437 .8 ..Bug 9651350 .8 .Bug 12582839 .8 .Bug 8428523 .8 .Bug 1400739 . ORA-1410.Bug 4592596 .Bug 1504967 .Bug 5523799 ."hcheck.ORA:1578 or ORA:8103 selecting invalid ROWID
NOTE:8740993.ORA-8103 possible on READ ONLY standby after TRUNCATE on primary
NOTE:136697.8 .Bug 1804299 .8 .Bug 9965085 .Large trace file for ORA-8103
NOTE:10329146.Bug 9272086 .Concurrent export / INSERT of ASSM segment can fail with ORA-1410 /
NOTE:12582839.How to identify the SEGMENT reported by dbms_space_admin.1 . Dump
when event 10736 level 4 is set
NOTE:8754670.How to identify the corrupt Object reported by ORA-1578 / RMAN / DBVERIFY
NOTE:6864586.8 .Wrong results.sql" script to check for known problems in Oracle8i.Alter Table Rename causes wrong results/ora-8103/hangs on ADG
Standby.Bug 7390324 .ORA-8103 possible from PQ on bitmap managed segments with
NOTE:12747437.Bug 10329146 .OERI:KCBGTCR_4 possible from long running DDL if referenced object
NOTE:4592596.8 . Trace file with Block type:
0x44=NGLOB: Extent Map
NOTE:1698789.Extract rows from a CORRUPT table creating ROWID from DBA_EXTENTS
NOTE:9659614.8 .8 .8 . Oracle9i.ORA-8103 by a query on DBA_EXTENTS.8 .Rollback of Direct load can corrupt BITMAP managed segments / ORA8103
NOTE:3868753.Bug 7710827 .8 .Bug 3966709 .Range/object reuse prematurely (ORA-8103)
NOTE:8428523.8 .8 .ORA-1578 / ORA-8103 Temporary table block corruption / space wastage
Page 11 of 12
NOTE:1504967.8 .Bug 6864586 .1 .Bug 3868753 .
8 .Bug 1283521 .8 .oracle.8 .ORA-8103 by DBA_UNDO_EXTENTS or
DBMS_SPACE_ADMIN.ORA-1410 or ORA-8103 by queries with DIRECT READ while
concurrent DIRECT INSERT
NOTE:9711472. Misplaced Blocks and Lost
Write in ASM
NOTE:9167831.Bug 10136415 .ORA-8103 ORA-600 ORA-3113 on temporary tables using INDEX FAST
FULL SCAN and DIRECT read
NOTE:11937253.ORA-8103 on operations for a partitioned LOB if any different partition is
NOTE:10136415.Bug 11850492 .SCRIPT to skip ORA-8103 ORA-1410 ORA-1578 ORA-600 [kdsgrp1] when reading a
https://support.ORA-8103 on Partitioned IOT after partition maintenance
NOTE:10209232.Bug 9275027 .1 .Bug 8725282 .8 .8 .ORA-1578 / ORA-600  Corruption..Document 8103.1 .8 .8 .Bug 10209232 .Bug 9167831 .8 .Bug 10385812 .8 .Bug 5637976 .
.8 .8 .Bug 6047085 .Corruption possible in automatic space managed segments
NOTE:1527738.8 .ORA-8103 possible in PQ slave
NOTE:2551000.Bug 8876094 .Bug 2333731 .Linux x64-64: SGA corruption / crash following any ORA-7445
NOTE:1283521.ctrl-state=enhk5u4ed_9.com/epmos/faces/DocumentDisplay?_adf.8 ..Lost Write in ASM when normal redundancy is used
NOTE:3785200.1 .ORA-8103 in a select at ADG standby database from table stored in ASSM
NOTE:2333731.False ORA-1410 / ORA-8103 possible from ANALYZE
NOTE:8876094.Extracting Data from a Corrupt Table using ROWID Range Scans in Oracle8 and higher
NOTE:8597106.Identify the corruption extension using RMAN/DBV/ANALYZE etc
NOTE:5637976.8 .Bug 9711472 .1
Page 12 of 12
NOTE:10385812.8 .Bug 7519406 .Corruption from cross platform transport of tablespace with securefile
NOTE:11850492.A Parallel query fails with ORA-8103 on an Active Dataguard
Enviroment.ORA-8103 instead of ORA-1410
NOTE:7519406.Bug 8597106 .Bug 2551000 .8 .Bug 11937253 .TABLESPACE_VERIFY on Block type: 0x25
NOTE:1053863.ORA-8103/ORA-1410 from concurrent INSERT / export on ASSM tables
NOTE:61685.8 .ORA-8103 can occur on TRUNCATED cluster table
NOTE:836658.8 .NCR: ORA-8103 / corrupt read possible using async IO
NOTE:6047085.8 .Bug 3785200 .ORA-600 [kcbnew_3] can occur after TRUNCATE / DROP
NOTE:8725282.Bug 1053863 .Bug 7650993 .Larger trace than needed for ORA-8103 under kteinicnt1