Re: FILE NEEDS MEDIA RECOVERY!

This is caused by the timestamp (last system change number) in the file's header being out of step with the corresponding entry in the control file(s) for the database. Ways that the files may get out of step are many and varied.

Did you ever switch the datafile(tablespace) into READ ONLY mode?

Did you restore an old backup of the datafile? Or controlfile? [nope, you said "no" to the controlfile swap].

It's 6am, so I might be wrong and/or incomplete - thinking about it over coffee #1.

JR

"Jack Jolly" <jgjolly_at_ingr.com> wrote:

>I've had the same db on the same server come up twice in the last two weeks
>with "file needs media recovery" on the same file.
>
>This is a non-archivelog db so I'm stuck going to my exports - but what is
>the root cause of this problem? No one has been doing anything funny like
>swapping control files or anything.
>
>The DB is split between internal drives and external drives - but even if
>the server had problems getting to the "external" files and the file was
>corrupt, wouldn't the db be startable - but perhaps with a "block xxx is
>corrupt" rather that a "file needs media recovery" error?
>
>I guess I'm looking for help as to what problems will result in the "file
>needs media recovery" error.
>
>Thanks!
>
>JJ
>===========================================================
>
> Jack G. Jolly
> Intergraph PDS Support
> jgjolly_at_ingr.com
>
>
Received on Tue Mar 09 1999 - 05:16:14 CST