Problem solving strategies sometimes find clear causes and answers and sometimes not, in this case analyzing the facts did show the way to find a workaround.
It happened on a multi TB RAC Database.
Symptoms observed were that queries on a partitioned table started to fail with ORA-1410 on some partitions.
The initial diagnostic was of a logical corruption affecting one specific datafile, in this case a shared raw device. Some of these partitions were dropped and recreated using create as select from a backup.
Once the create as select finished, checkup on the new partitions again returned ORA-1410, all traces pointing to the same raw device.
The common factor was always the same device. Building a new raw device and moving all partitions siting on the affected one solved the problem.
« Database location on the storage frame | Main | Log Miner Implementation Summary »
ORA-1410 invalid row id
TrackBack
TrackBack URL for this entry:
http://blogs.oracle.com/mte1521/mt-tb.cgi/4316
Search All Blogs
Google Search
About This Entry
This page contains a single entry from the blog posted on July 22, 2007 7:07 PM.
The previous post in this blog was Database location on the storage frame.
The next post in this blog is Log Miner Implementation Summary.
Many more can be found on the main index page or by looking through the archives.
