It would be good to see what is showing up in the alert logs, but sometimes
you can fix issues by cancelling and restarting managed standby or by
setting the log_archive_dest to defer, then enable.
On Thu, Sep 16, 2021 at 3:32 PM Upendra nerilla <nupendra@xxxxxxxxxxx>
wrote:
On your primary db, you could disable and enable the standby arch dest..
that might fix it.
------------------------------
*From:* oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on
behalf of Scott Canaan <srcdco@xxxxxxx>
*Sent:* Thursday, September 16, 2021 3:53 PM
*To:* 'oracle-l@xxxxxxxxxxxxx' <oracle-l@xxxxxxxxxxxxx>
*Subject:* Data Guard Issue
Earlier today, I had the sysadmins add disk space to the physical standby
server. Apparently the interruption to do that was longer than data guard
liked. It stopped sending the logs from the primary to the standby. I
have manually caught up by copying the missing logs and registering them
with the standby. It applies them as soon as I do that, but any newer logs
are not being shipped from the primary to the standby. I can’t figure out
why and how to fix it.
This is Oracle 19c on Red Hat 7.
*Scott Canaan ‘88*
*Sr Database Administrator *Information & Technology Services
Finance & Administration
*Rochester Institute of Technology *o: (585) 475-7886 | f: (585) 475-7520
*srcdco@xxxxxxx <srcdco@xxxxxxx>* | c: (585) 339-8659
*CONFIDENTIALITY NOTE*: The information transmitted, including
attachments, is intended only for the person(s) or entity to which it is
addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon this information by persons or entities other than
the intended recipient is prohibited. If you received this in error, please
contact the sender and destroy any copies of this information.
