RE: Tracing invalid rowid ora-01410

  • From: "Laimutis Nedzinskas" <Laimutis.Nedzinskas@xxxxxxxxxxxxx>
  • To: <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 2 Aug 2006 12:11:53 -0000

Is it really so? 
Consistency is enforced bellow indexes or tables. It is enforced at
block level.
The previous version of the index should still see the previous version
of the table blocks, shouldn't it? 

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jonathan Lewis

Possible cause:

ORA-01410 can be the result of one session working through a long
running query that depends on an index that gets rebuilt by another

The index "moves", but the first session is still using the previous
version of the index (read consistency across DDL).  If the space freed
by the rebuild is then re-used, the first session is likely to crash
with a 1410.


Other related posts: