Re: What would cause ORA-1410 (invalid rowid) on a simple select?

Anurag Varma wrote:
> On Aug 30, 4:02 pm, Chuck <skilover_nos..._at_bluebottle.com> wrote:

>> Oracle 10.2.0.2 64 bit, Solaris 10.
>>
>> Here's the select? Occasionally we get an ORA-1410 on it but 99.9% of
>> the time it works fine. It's coming from a web based application that
>> uses a product called hibernate to access to the database.
>>
>> SELECT DISTINCT flipbook2_.name AS col_0_0_
>> FROM flip_page_media flippageme0_,
>>     flip_page flippage1_,
>>     flipbook flipbook2_
>>     INNER JOIN user_content flipbook2_1_
>>        ON flipbook2_.content_id = flipbook2_1_.content_id
>>     INNER JOIN content flipbook2_2_
>>        ON flipbook2_.content_id = flipbook2_2_.content_id
>> WHERE flippage1_.content_id = flipbook2_.content_id
>>   AND flippageme0_.flip_page_id = flippage1_.flip_page_id
>>   AND flippageme0_.media_id = :1
>>
>> I have checked the indexes used for corruption and found none.

That's what I thought too. The only time I've even seen this before was with incorrect use of a "where current of" cursor.

> How did you check the indexes for corruption?
>
> Did you issue an alter table <table> validate structure cascade; ? to
> see
> if there is a rowid mismatch between the table and index.

Yes. I also ran dbv on the datafiles in the index tablespaces.

I am wondering if there is a with the INNER JOIN syntax. That same syntax has caused problems in defining materialized views before and I had to convert it to the older style join syntax before it would work. Unfortunately in this case it's being generated by a 3rd party product from behind the scenes. Received on Thu Aug 30 2007 - 15:56:55 CDT