RE: arch slow and standby.

Ankur,  

As Igor (igor.polishchuk_at_convergys.com
<mailto:igor.polishchuk_at_convergys.com> ) pointed out in his post, he experienced this problem as did we at our site due to a slow WAN. Oracle Support directed us to this parameter. At the time we were on 9205, but have since upgraded to 9207. After upgrading, we never unset the _LOG_ARCHIVE_CALLOUT='LOCAL_FIRST=TRUE' hidden parameter, but it doesn't appear to be a problem. I only point this out because when I reread the Metalink note, 260040.1, it looks like Oracle has changed this to the default behavior in since 9207.  

Cheers,  

David Taft  

-----Original Message-----
From: igor.polishchuk_at_convergys.com [mailto:igor.polishchuk_at_convergys.com] Sent: Tuesday, April 10, 2007 2:30 PM
To: oracle-l_at_freelists.org
Subject: RE: arch slow and standby.

Ankur,

On 9i, when a network connection is not dead but just slow, you may have a problem. I've experienced problems with a live database. It actually hanged under heavy load.

I may not remember exact details, but it was definitely a problem because archiver waited until remote archive would be created.

To fix this situation, look at hidden parameter _log_archive_callout and set it to 'LOCAL_FIRST=TRUE'. If you make a search on metalink, you'll find an article describing exactly mentioned above behavior and recommending the mention parameter setup.

I did not have a chance to really test it on a slow network myself yet.

--
http://www.freelists.org/webpage/oracle-l