Re: Disabling ARCHIVELOG problem

> Hi Chloe,
>
> The "problem" is this. You currently have a file that Oracle believes
> requires media recovery. Basically the header on this file is not in sync
> with the rest of the database. Why is this the case, who knows ? Perhaps the
> tablespace was taken offline "immediate" or some such at some point in
> time...
>
> The point though is that to get this file to resync with the rest of the
> database, Oracle needs to apply all the redo from 6/11/04 until the current
> point in time, where 6/11/04 is the date of the checkpoint info in the
> header of this problem data file. It must apply *all* the redo from this
> time up to the *current point of time* else it can't possibly be resync'ed.
>
> If you were to now disable archiving, Oracle has no way of *guaranteeing*
> all the necessary redo logs will be available. You overwrite a redo log
> without archiving it and all chance to recover this file is gone as you will
> have created a "hole" in the redo stream.
>
> Therefore Oracle is trying to protect you. It will not allow you to
> "abandon" this poor file by allowing you to disable logging as such
> abandonment will likely render recovery impossible.
>
> So you either recovery it in which case all is well again, the *whole*
> database is now in sync and you can disable away. Or you drop the tablespace
> as it's a useless limb ready for amputation until it's recovered anyways.
>
> Make sense ?
>
> Cheers
>
> Richard

Richard

thanks for this. I've discovered how it happened (my boss was adding datafiles in my absence, made a mistake and left an offline datafile *without telling me*). There won't actually be any data blocks in the file.

There's is no chance of recovering from mid-June, we simply don't have archivelogs going back that far (8 weeks would be the far limit, and even that would be tricky). Equally I can't simply drop the tablespace since it contains significant amounts of production data (and seems to be working correctly).

If we created a new tablespace, with new datafiles, and moved the tables to the new tablespace, would this clear the problem?

Chloe Received on Wed Sep 01 2004 - 04:01:25 CDT