Re: Standby Database performance

From: kapil vaish <>
Date: Wed, 23 Nov 2011 06:47:22 -0800 (PST)
Message-ID: <>

Thanks Alan for your comments. Our standby is lagging behind even with this apply rate and we have to often use RMAN to sync it  up.  

From: Guillermo Alan Bort <> To:
Cc: "" <> Sent: Wednesday, November 23, 2011 5:53 AM Subject: Re: Standby Database performance

<disclaimer>this is a strictly unhelpful comment </disclaimer> I'm curious as to why you want to further reduce the apply time. Are you experiencing a delay in the standby because it takes 45 seconds to apply the archivelogs?

One of the key concepts of tuning in knowing when to stop, so perhaps if you are experiencing no problems with this apply time it's time to leave it be and move on to the next problem (there's always a next problem... otherwise life would be boring)

hope that wasn't too unhelpful

On Tue, Nov 22, 2011 at 4:23 PM, kapil vaish <> wrote:

> Hi Guys ,
> we have physical standby database for one of our biggest database. Scripts
> ship the archived log to standby server and then using parallel 32, manual
> recovery is performed (thru scripts) . Archived log size is 2 GB and daily
> production archive generation is aorund 2.5 TB. We are trying to increase
> performance on our standby database. We tried tuning various standby
> related parameters and IO, maximum apply rate we could achieve is 45 sec
> per archive log.  Can you suggest any other tunings you may have seen in
> your environments ? any pointers are appreciated ..
> thanks
> kapil Vaish
> --

Received on Wed Nov 23 2011 - 08:47:22 CST

Original text of this message