Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: ORA-1578...block corrupted...error is normal...a block...had a NOLOGGING...operation performed against
On 8/19/05, Joel Garry <joelgarry_at_anabolicinc.com> wrote:
>
>
> Believe it. Time bomb sat there since long ago. Nologging operations
> bypass the redo logs. So they bypass the archived logs. So when you
> restore the datafile by rolling forward, you invalidate those blocks.
Roll forward from when?
If you restore from a backup prior to the nologging operation, and roll forward, the index created with 'nologging' will not be restored.
If you restore a backup taken after the creation of the nologging operation, the nologging object will be restored.
So you have to fix them with some other mechanism than recovery. Maybe
> use force logging if you don't want to run into this again. And all
> that advice about taking a backup after nologging operations seems
> pretty misleading, huh?
Either you need to test it further, or I don't understand your premise.
-- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist -- http://www.freelists.org/webpage/oracle-lReceived on Fri Aug 19 2005 - 14:33:30 CDT
![]() |
![]() |