Applying logs to standby in 11g

From: Sandra Becker <sbecker6925_at_gmail.com>
Date: Mon, 22 Oct 2012 12:32:07 -0600
Message-ID: <CAJzM94Dgc+NR40xVp+jAzkui2cRz+0DW4QxgkqF94c3DKxZPYw_at_mail.gmail.com>



This pas weekend I upgraded my production OLTP from 10g to 11g (SUSE11 on IBM zLinux), then I created an 11g standby. We moved the database to newer, faster, correctly configured storage at the same time. All went well and everything is functioning better than it did before the upgrade. My question is regarding the value in the applied column of v$archived_log.  Under 10g the value was changed to 'YES' within a few minutes, or less, for smaller logs such as less than 1M. Under 11g I don't see that changing until a log switch so it appears I am a log behind. I can see the messages that media recover has started for one log followed by a message that another log is in transit so I am assuming that the first log has been successfully applied, but v$archived_log still shows it isn't applied.  Perhaps that's not a valid assumption.

.
.
.

Media Recovery Log /u06/oradata/prod/arch/1_304_797150180.arc Media Recovery Waiting for thread 1 sequence 305 (in transit)

Question: Is this normal behavior in 11g? If not, where should I look to see what the cause is? I've been searching MOS and Google but haven't seen this scenario addressed yet.

Thanks in advance.

-- 
Sandy
Transzap, Inc.


--
http://www.freelists.org/webpage/oracle-l
Received on Mon Oct 22 2012 - 20:32:07 CEST

Original text of this message