sounds like you've successfully recovered. Now, the problem w/ the
"missing" rows. This may be where NOLOGGING is relevant. How is this
data loaded? If it was done as INSERT /*+ APPEND */, then the problem is
that, with nologging set, the data was not in the archive logs you applied, so,
the segment will need to be truncated and reloaded. Ideally, the table is
partitioned (is it?) so that you can truncate and re-load just that
partition. Right now, if you do a full table scan of the segment, your
query will eventually hit the logically corrupt blocks and raise an
ORA-26040. The only way to get rid of those corrupt blocks is to either
drop or truncate the segment containing them.
Mark J. Bobak
Senior Oracle Architect
ProQuest Information & Learning
For a successful technology, reality must
take precedence over public relations, for Nature cannot be fooled.
--Richard P. Feynman, 1918-1988
We used the following syntax to recover a database
ALTER DATABASE RECOVER DATABASE UNTIL TIME '2006-05-10:09:00:00' USING
Some of the archive files said "no longer needed for recovery"
Now, we are told there are rows missing from the night of the 9th (i.e. the
New Yahoo! Messenger with Voice. Call
regular phones from your PC
and save big.