I have seen it, it is described in the MOS document 1308804.1. This
seems to be a bug and the solution is:
Solution
Set the log_archive_trace to 0 like,
alter system set log_Archive_trace=0;
on both primary and standby if it is set before.
In DGMGRL,
DGMGRL>edit database '<database>' set property LogArchiveTrace=0;
References
BUG:10331312
<https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1308804.1&id=10331312>
- LOG_ARCHIVE_DEST_2 DEPENDS UPON ME, BUT MY DESTINATION INDEX 2 DOES
NOT MATCH IT
This is, of course, a cut and paste from the listed MOS document. As has
become customary in recent years, there is no explanation or root cause,
just a workaround. I have only seen it happen in version 11 on Solaris,
although the document says that the bug is generic. May the force be
with you.
On 04/27/2017 11:22 AM, Howard Latham wrote:
11.2.0,4 Redhat Linux
Does anyone know about this error?
This was in a trace file. I ask because I have a problem getting log shipping working.(yes we had to get a new server after failure!!)
*** 2017-04-27 15:55:59.807
*** 2017-04-27 15:55:59.807 2167 krsd.c
LOG_ARCHIVE_DEST_5 depends upon me, but my destination index 3 does not match its destination index 4
--
Howard A. Latham
