Re: Archive logs applied on remote physical standby not updated on primary
Date: Fri, 23 Mar 2012 08:38:13 -0700
I have yet to find a single method that always works for similar situations.
Some things to try are:
Play around with the basic parameters in an effort to kick start the transfer. (e.g. on the primary, set the log_archive_dest_X (going to the standby) to reset and back to enable) If this doesn't work, restarting the standby might... And if that doesn't work and you're in a DG broker configuration, remove db from it or drop configuration entirely and re-add/recreate --I've had primary/standby communication situations where everything I tried failed and recreating the configuration fixed it.
On Fri, Mar 23, 2012 at 7:53 AM, sundar mahadevan
> Update: Found note: *263994.1* reporting similar issue but does not suggest
> a solution.
> On Fri, Mar 23, 2012 at 10:47 AM, sundar mahadevan <
> sundarmahadevan82_at_gmail.com> wrote:
>> Hi All,
>> Good day. I have a physical standby setup and the archived location on the
>> standby got filled up. After cleaning up the disk, I manually copied the
>> archived log files from primary to standby, registered the files and
>> started "RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION". Standby
>> is in sync with primary now. But primary still is not updated with the
>> information that these archive logs got applied on standby. Is there any
>> way to reset this information? thanks.
>> I am on 10gR204 on 64 bit SLES 11(both primary and standby).