Wednesday, January 27, 2016
ORA-08103 object no longer exists
check alert log
block corruption
analyze validate structure
Doc ID 8103.1
You can try to drop and rebuild the index(es) and see whether it solves the problem.
UNDO_RETENTION
ORA-08103 object no longer exists
Cause: The object has been deleted by another user since the operation began. Or a prior incomplete recovery restored the database to a point in time during the deletion of the object
Action: Remove references to the object or delete the object if this is the result of an incomplete recovery.
http://www.dba-oracle.com/t_ora_08103_object_no_longer_exists.htm
There are several likely reasons for this error, and you should always check your alert log for details. This error often requires opening a service request with MOSC:
0: A software bug (see list below).
1: You are not signed-on as the table owner.
2: Database corruption of a header block.
3: Accidental delete of the target table. (check the recyclebin)
4: Data file I/O error (check alert log)
5: corruption in UNDO log (drop and re-create)
6. An index is disabled or is offline.
Possible solution include:
1: Set db_file_multiblock_read_count to 1.
2: Run dbv on all data files.
3: Run catalog.sql, catproc.sql and utlrp.sql to ensure no data dictionary corruption.
4: Purge recyclebin & dba_recyclebin.
5: When the ORA-08103 is on an index operation, place the index online or make index usable
select index_name , status from user_indexes;
INDEX_NAME STATUS
------------------------------ --------
IDX_CUST UNUSABLE
alter index idx_cust rebuild online;
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment