Replication, even with Data Guard Broker, can be a challenge sometimes, especially if replication stops, and everything looks OK, leading to the Big Question: What's wrong with the #@!% thing?!
If all else fails, it may be worth taking a look at Archive Dest status on the Primary instances.
Unhelpfully, logging in to SQL*Plus and issuing "SHOW PARAMETER ARCHIVE_DEST" will not, necessarily, show in-error archive dest.
col DEST_NAME form A25
col DESTINATION form A20
col STATUS form A20
--
select DEST_NAME,DESTINATION,STATUS,ERROR
from V$ARCHIVE_DEST_STATUS
order by STATUS,DEST_NAME;
from V$ARCHIVE_DEST_STATUS
order by STATUS,DEST_NAME;
If you see "ERROR" in the STATUS column, then re-enable the archive dest.
No comments:
Post a Comment