Re: Standby db Real Time Apply (10gR2)
Date: Tue, 4 Nov 2008 09:00:18 -0800 (PST)
On Oct 28, 3:24 pm, Steve Howard <stevedhow..._at_gmail.com> wrote:
> Have you actually created the standby logs with the same size as the
> primary's online redo logs? Oracle won't return an error if you
> haven't, but it will silently throw the exception you noted.
> If you have created them, I would make sure the standby is actually
> caught up. One view (among others like v$dataguard_stats) you can use
> is v$standby_apply_snapshot. Assuming you are using maximum
> performance mode on the primary, then if that view is not yet
> populated (or the time is not relatively current, less than a minute
> behind or so), you may not yet have the transaction on the standby.
> Wait until you see it "caught up" and you should see the transaction.
Steve, thanks for your response.
SQL> select sequence#,SNAPSHOT_TIME,APPLIED_TIME from V $standby_apply_snapshot;
SEQUENCE# SNAPSHOT_TIME APPLIED_TIME
---------- -------------------- -------------------- 117 04-nov-2008 10:15:22 04-nov-2008 08:42:51
seq#117 was the last successful available log applied. There were no other logs to be applied. When I committed an insert statement on the primary db, I still did not receive the transaction on the standby db until I switched logfile on the primary db.
As mentioned earlier, whenever I cancel the recovery process, I've
"ORA-16037: user requested cancel of managed recovery operation Managed Standby Recovery not using Real Time Apply"
Anyone experience the same issue on Linux AS 4.0, 10.2.0.3?
Thanks. Received on Tue Nov 04 2008 - 11:00:18 CST