Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Corrupted Redo Logs
Seems when I added another member (multi-plexing) to my REDO logs, I saw the
word STALE . I don't think I needed to do anything, but I did a 'alter
system switch logfile' and it cleared up the current REDO group status.
So, the STALE status doesn't mean corrupted I assume.
Seems to me if you have a corrupted log file, then you would not be able to completely/cleanly do a switch logfile... which activates the log writer to copy the log to the archived log dest.
Not sure why you have this status to begin with ?
Do you see any other errors like in the alert.log ? That would be a good place to see any errors about a corrupt file anywhere I think. Or , looking in the /var/adm/messages file (for Solaris Unix anyway). I have seen other people comment on the use of a utility to check Oracle files which I have never used (called something like dbverify - look in ORACLE_HOME/bin/db*).
Anyway, just my opinion... check the manuals wouldn't hurt - maybe search for "corrupt file" .
"Kevin McDaniel" <kmcdaniel96_at_attbi.com> wrote in message
news:60115ff8.0302151844.7e1fd661_at_posting.google.com...
> 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 - 01:48:36 CST