ORA-08176: consistent read failure; rollback data not available
OracleWhat does it mean?
While building a consistent read image, a query encountered blocks modified by an operation that generates no undo; since no undo/rollback data exists for these blocks, the consistent image could not be built. Unlike ORA-01555, the undo was never generated rather than overwritten. (The serializable isolation error is a separate code: ORA-08177.)
Why does it happen?
An operation that generates no undo runs on the same object while the query is in progress: direct-path loads (INSERT /*+ APPEND */, SQL*Loader DIRECT=TRUE), CREATE INDEX / index rebuild or discrete transactions.
How to fix it
Rerun the query after the direct-path load or index operation has finished (retry). Do not schedule long reports and direct-path load / index maintenance jobs on the same object in the same time window. If it recurs, identify the conflicting job with the alert log and ASH and separate the schedules.
More from this engine
- ORA-04021timeout occurred while waiting to lock object
- ORA-04061existing state of package/procedure has been invalidated
- ORA-01466unable to read data - table definition has changed
- ORA-00020maximum number of processes (N) exceeded
- ORA-01113file N needs media recovery
- ORA-02393exceeded call limit on CPU usage
- ORA-12801error signaled in parallel query server Pnnn