OERR: ORA-8103 "Object No Longer Exists" Primary Note / Troubleshooting, Diagnostic and Solution (Doc ID 8103.1)

Last updated on FEBRUARY 23, 2023

Applies to:

Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Purpose

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

Scope

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

Details

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Expected behavior.

Block Corruption.

Overlapped Extents.

Overlapped ASM extent.

Identify the affected object

Get the SQL statement that is causing the error.

Identify the affected object in trace file section "dump suspect buffer".

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.

ORA-8103 in XML objects

Fix Block Corruption.

Flush the buffer cache.

Flush the shared pool.

Index Corruption.

Table Corruption.

OPTION 1 - No backup

OPTION 2 - No backup

Temporary Segment Corruption

Fix Overlapped Extents.

Known Bug Issues

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.