Oracle Database
An insert can fail when its segment cannot obtain another extent. Check allocated file capacity, growth limits and real storage headroom together.
Storage, Undo & Redo1 min read
Read article : ORA-01653: diagnose a table extent allocation failure
Oracle Database
An insert may fail while extending an index even when its table tablespace has room. Use the tablespace and index named in the error.
Storage, Undo & Redo2 min read
Read article : ORA-01654: investigate index tablespace growth separately
Oracle Database
A temporary-segment allocation failure can involve TEMP or work performed in another named tablespace. Start with the complete error and operation.
Storage, Undo & Redo1 min read
Read article : ORA-01652: identify the segment and tablespace needing temporary allocation
Oracle Database
A user can exhaust its allowed allocation while the tablespace itself still has room. Inspect the quota for the account named by the failing operation.
Storage, Undo & Redo2 min read
Read article : ORA-01536: check an account's tablespace quota
Oracle Database
Creating a table can appear to work with deferred segment creation, then the first insert fails because the owner cannot allocate storage.
Storage, Undo & Redo1 min read
Read article : ORA-01950: diagnose missing allocation rights in a tablespace
Oracle Database
A write-heavy transaction may fail when undo cannot extend. Active transactions, retention settings and storage limits all affect available undo.
Storage, Undo & Redo1 min read
Read article : ORA-30036: investigate undo tablespace exhaustion
Oracle Database
A long query can lose needed older block versions while other transactions generate undo. Capture query duration and the failing workload interval.
Storage, Undo & Redo2 min read
Read article : ORA-01555: correlate consistent-read failures with undo pressure
Oracle Database
A scan can fail when its referenced object changes, for example during concurrent truncation or partition maintenance. Preserve the SQL and maintenance timeline.
Storage, Undo & Redo2 min read
Read article : ORA-08103: investigate object changes during a scan
Oracle Database
Oracle may be unable to identify or lock a datafile because storage, file identity or access is wrong. Read the accompanying errors and file number.
Storage, Undo & Redo2 min read
Read article : ORA-01157: identify an inaccessible datafile before recovery
Oracle Database
A restored or inconsistent file may need redo application before it can be used. Establish the file and database recovery state.
Storage, Undo & Redo1 min read
Read article : ORA-01113: determine why a datafile requires media recovery
Oracle Database
This message commonly identifies the datafile associated with another error. Preserve the complete stack so the actual failure is not lost.
Storage, Undo & Redo1 min read
Read article : ORA-01110: use the accompanying file detail rather than treating it as the cause
Oracle Database
A block-corruption report needs file and block identifiers, affected objects and storage context. Avoid unplanned repair that could discard data.
Storage, Undo & Redo2 min read
Read article : ORA-01578: preserve evidence of a corrupt Oracle block