RE: Recovery Issues :)

Hi Paula,
 
Ok, it 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.
 
For more info on direct load, nologging, and recovery implications, see:
http://dizwell.com/main/index.php?option=com_jd-wiki&Itemid=138&id=direc
tpathoperations
 
Hope that helps,
 
-Mark
 

-- 
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

 

________________________________

From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Paula Stankus
Sent: Thursday, May 11, 2006 11:59 AM
To: Christo Kutrovsky
Cc: Oracle-L@xxxxxxxxxxxxx
Subject: Re:Recovery Issues :)


Okay,
 
We used the following syntax to recover a database 
 
ALTER DATABASE RECOVER DATABASE UNTIL TIME '2006-05-10:09:00:00' USING
BACKUP CONTROLFILE
 
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 night before).  
 
Help :)!

________________________________

New Yahoo! Messenger with Voice. Call regular phones from your PC
<http://us.rd.yahoo.com/mail_us/taglines/postman5/*http://us.rd.yahoo.co
m/evt=39666/*http://messenger.yahoo.com>  and save big.

Other related posts: