Re: Standby database: Skipping logs?

The docs as you state them are correct, as is what you expect from them!

So when you say it's skipping logs, you mean that it is failing to transfer some logs, to a mandatory destination? (I presume (and hope) that you are not saying that the standby only *applies* some of the logs!!)

You (or a colleague) haven't ever changed that destination's state to 'defer' have you?

Otherwise, you need to poke around in side the trace files for the relevant arch process, and the rfs process on the standby site, and maybe get some idea of what is happening.

Regards
HJR "Vikas Agnihotri" <onlyforposting_at_yahoo.com> wrote in message news:77e87b58.0107021916.19659d2a_at_posting.google.com...
> No. As per the docs, the MANDATORY clause in the LOG_ARCHIVE_DEST_n
> parameter suffices. Making a DEST mandatory should make Oracle treat
> the dest as dearer than life. i.e. it would do everything in its power
> (including stopping the database) to write that destination before it
> over-wrote online logs. Just like it does for the regular
> log_archive_dest.
>
> Thats why I was shocked to see Oracle merrily recycle online logs
> before it successfully wrote the remote archive log.
>
> Is it just me? Has anyone else used the standby database feature in a
> production environment with a large volume of redologs (10M of redo
> per second during peak period lasting about 1 hour).
>
> Vikas
>
> "Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message
 news:<3b40a7e4$0$8511$ed9e5944_at_reading.news.pipex.net>...
> > There is a parameter MIN_ARCHIVE_SUCCEED_DEST (or something very
 similar)
> > which controls how many of the archive destinations a redo log has to be
> > written to before oracle considers the write successful. I believe the
> > default for this parameter is one.
Received on Sat Jul 21 2001 - 16:25:16 CDT