Re: Tracing invalid rowid ora-01410
- From: Deepak Sharma <sharmakdeep_oracle@xxxxxxxxx>
- To: jonathan@xxxxxxxxxxxxxxxxxx, oracle-l@xxxxxxxxxxxxx
- Date: Wed, 20 Sep 2006 09:50:54 -0700 (PDT)
It's been very long since I originally posted the
question (and never got a chance to look at the
replies). But, you're absolutely correct. We had an
online index rebuild job that was causing the error on
the queries that referenced the same table at that
very instant. Did not always happen, but whenever it
did, we had the index rebuilds running. We just moved
the index rebuild to a non-active time of the week,
and that has been working for us.
Thanks,
Deepak
--- Jonathan Lewis <jonathan@xxxxxxxxxxxxxxxxxx>
wrote:
>
> Yes, it really is so.
>
> If you re-use the space where the index used to be,
> the run-time engine won't see the old index block -
> it will see a block that belongs to a completely
> different object. (Remember that Oracle navigates
> through indexes using block ids. Rowids are only
> used to get from index leaf blocks to table blocks.)
> The object_id mismatch will result in Oracle error
> ORA-01410 - unfortunately it's an error number
> that has been hijacked and mis-used, so the text
> is not appropriate for this specific problem.
>
> I think the last time I checked this was Oracle
> 9.2.0.4,
> so I guess I'll have to check if things have changed
> recently.
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
//www.freelists.org/webpage/oracle-l
Other related posts:
