Re: MANAGED STANDBY PROBLEM

Woah, it took me a long time to figure out what the error message was. Found this note in my oracle support:

    LOG_ARCHIVE_DEST_<> DEPENDS UPON ME, BUT MY DESTINATION INDEX <> DOES NOT MATCH IT (Doc ID 1308804.1)

It looks like information message due to log_archive_trace. So you need to turn it off at both the primary and standby:

    SQL> alter system set log_Archive_trace=0;

As for the strange v$archive_dest_status, please show us what's wrong with it. Have you looked at v$managed_standby, v$archived_log?

HTH, Leng.

On Wed, Aug 1, 2018 at 11:06 PM, Howard Latham <howard.latham_at_gmail.com> wrote:

> All view and suggestions on this problem welcome!
>
> Oracle 11.2.04 RH ENT 5
>
> Using physical standbys, Not using dataguard broker.
>
> we have 1 primary and 2 standbys - both are are up to date and applying
> logs happily but
>
> v$archive_dest_status is giving a crazy - very low wrong applied log number
>
> and the following error appears in the nsa trace file.
>
> LOG_ARCHIVE_DEST_6 depends upon me, but my destination index 4 does not
> match its destination index 5
>
> A clue is we get the wrong number even when the standby giving the wrong
> number is down.
>
> Have tried bouncing both standbys.
>
>
>
>
> Howard A. Latham
>
>
>

--
http://www.freelists.org/webpage/oracle-l