File Corruption

[Kevin Stussman]

We have DB consultants here that must have missed this piece
of info re: "inserted after the online redo log is successfully
archived". I'm not a Oracle expert, all I know is that rsync
sees a file that needs transferring (completed or not).

The bit about rsync behavior was just a suggestion for a situation where
something like V$ARCHIVE_LOG was not available. I wasn't sure if
--check-source-file-change (or whatever) would be a useful feature.

K.


On Mon, 2005-09-12 at 13:15 -0400, Linus Hicks wrote:
> Stefan Nehlsen wrote:
> > On Mon, Sep 12, 2005 at 09:36:27AM -0600, Kevin Stussman wrote: 
> > rsync will have a second try if this happens and I think it will warn.
> > 
> 
> This seems like a waste of resources to me. Why not query V$ARCHIVE_LOG?
> 
>  From the manual:
> 
> This view displays archived log information from the control file, including 
> archive log names. An archive log record is inserted after the online redo log 
> is successfully archived or cleared (name column is NULL if the log was 
> cleared). If the log is archived twice, there will be two archived log records 
> with the same THREAD#, SEQUENCE#, and FIRST_CHANGE#, but with a different name. 
> An archive log record is also inserted when an archive log is restored from a 
> backup set or a copy and whenever a copy of a log is made with the RMAN COPY 
> command.