Re: ORA-01499

Hi Fance,

from the trace file you should see which rows have a problem. Note the rowid which is mentioned there. Select from the table with the rowid hint and compare the the values with the entries in the trace files (which are the values of the index) Are there any inconsistencies?.
Delete the problematic rows and insert them again.

Hope this helps
Stefan

Vance Wu wrote:

> Hi,
>
> Anybody out there experienced "ORA-01499 table/Index Cross Reference
> Failure - see trace file." and knowing how to interpret the trace
> file. Error occurred when I ANALYZE the table to validate the
> structure of the table's indexes using CASCADE clause:
>
> ANALYZE TABLE mytable VALIDATE STRUCTURE CASCADE;
>
> Even dropping and recreating the indexes did not work, I also ANALYZE
> individual indexes to verify the integrity of each data block in the
> index and check for block corruption:
>
> ANALYZE INDEX myindex VALIDATE STRUCTURE;
>
> And intermittently found block corruption in some indexes, but it is
> fixable by dropping and recreating the indexes. I kept
> dropping/recreating the indexes until all indexes are fixed, but never
> able to ANALYZE TABLE successfully using VALIDATE STRUCTURE CASCADE
> clauses as mentioned above.
>
> Oracle MetaLink note# 1081343.6 said "Recreating the table via
> export/import and then creating the indexes resolved the issue.", I
> followed what they said without any luck.
>
> 'mytable' contains five partitions, is the problem related to
> partition issue? or is it just another Oracle bug? they blame on
> hardware: "This was most likely caused by some type of hardware
> problem as the problem failed to be reproduced in house." (see note)
> which I don't believe. This problem happened on both
> Oracle 8.1.6 (installed on Solaris 2.6), and Oracle 8.1.7 (installed
> on Linux Redhat 6.2).
>
> Any help would be appreciated.
>
> Vance.
Received on Wed Jan 09 2002 - 00:16:50 CST