Re: Corrupted Redo Logs

Kevin,
you will be quite sure your logfile is corrupt; don't worry. First of all your archiver will be stuck (unable to archive file ...) then your users will start complaining ("we get an Archiver stuck message") then you check you Alert file and find lots of error messages.

Stale = no trouble at all; it's just partially filled.

     Roelof Schierbeek

R.Schierbeek, DBA
e-mail: infoNotospm_at_bytelifeNotospm.com
sql : www.bytelife.com/sql4dba.htm
Kevin McDaniel <kmcdaniel96_at_attbi.com> schreef in
> I'm reading up on the Backup and Recovery study materials and it talks
> about clearing corrupted redo logs. Specifically, it states "If an
> online redo log file has been corrupted while the database is open,
> ALTER DATABASE CLEAR LOGFILE can be used to create or clear the files
> without the database needing to be shut down." That's cool, but I'm
> trying to understand how a DBA would KNOW that the file was corrupted,
> versus anything else. It mentions querying the v$logfile view and
> looking at the status column (INVALID=inaccessible, STALE=contents
> incomplete because file not filled, blank=in use). Does this mean
> that if I have a STALE member, I've got a corrupted file? How can I
> be certain the file is corrupted so that I can take appropriate
> action? Appreciate all serious replies in advance. Thanks.
>
> Kevin
Received on Sun Feb 16 2003 - 05:09:55 CST