Take a look at using Real Time Apply if there is not a requirement to keep the standby behind. I actually worked at a company where the standby lagged primary by 18 hours. The purpose was backup and to roll back batch jobs gone bad in the evening versus having to recover large database. Michael Dinh. ________________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Niall Litchfield [niall.litchfield@xxxxxxxxx] Sent: Tuesday, December 21, 2010 11:07 PM To: krish33moorthy@xxxxxxxxx Cc: oracle Freelists Subject: Re: DG Scheduled log shipping at DR site Hi If I understand you correctly, then you have large logs that switch rarely - and therefore you have spikes of bandwidth consumption at a log switch? If so then the parameter ARCHIVE_LAG_TARGET on the primary would seem designed for your requirements, I personally like a period of 15 minutes rather than an hour. Further forward you might wish to consider if large archives are appropriate. If I've misunderstood then the above is irrelevant. On Wed, Dec 22, 2010 at 2:57 AM, KRISHNA MOORTHY <krish33moorthy@xxxxxxxxx<mailto:krish33moorthy@xxxxxxxxx>> wrote: Hi All, We have Oracle 10g dataguard configuration - primary and DR site. Per day 3G logs are transferred to DR site.It fully utilize the network bandwidth.(2MBPS) Is there any possible way for an scheduled log shipping? (one hour)... Regards Krishna 9585354917 -- Niall Litchfield Oracle DBA http://www.orawin.info -- //www.freelists.org/webpage/oracle-l