Backing up immediately after a NOLOGGING operation may well be your best
bet. (Aside, perhaps, from not doing nologging operations in the first
place.) But the backup need not be a FULL backup; an incremental is just as
good. Or, at least, so say the doc's.
>
> On 5/11/06, Paula Stankus <paulastankus_at_yahoo.com> wrote:
> >
> > We had a database with some tablespaces marked as nologging
> >
> > Sys admin. copied files from backup on top of those files (hot backup)
> >
> > Tablespaces with "nologging" complianed about needing media recovery.
> >
> > Is the only way to circumvent this problem be to backup immediately
> > after loads?
> >
> > Question: Would flash recovery assist in recovery when datafiles are
> > deleted or corrupted?
> >
> > ------------------------------
> > How low will we go? Check out Yahoo! Messenger's low PC-to-Phone call
> > rates.
> > <http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com>
> >
> >
>
--
Cheers,
-- Mark Brinsmead
Staff DBA,
The Pythian Group
http://www.pythian.com/blogs
--
http://www.freelists.org/webpage/oracle-l
Received on Thu May 11 2006 - 20:20:28 CDT
