RE: arch slow and standby.

So the assumption that database will hang in case of slow archival to remote destination even when log_archive_dest_n is optional is true for 9i unless _LOG_ARCHIVE_CALLOUT='LOCAL_FIRST=TRUE' parameter is set. The parameter directs arch to archive to local destination first and then to remote.

Thanks to David for pointing out the metalink doc - Note 260040.1.

Regards,

Ankur  

From: Taft, David [mailto:TaftD_at_saic-dc.com] Sent: Tuesday, April 10, 2007 9:22 PM
To: Ankur Godambe; oracle-l_at_freelists.org Subject: RE: arch slow and standby.  

Ankur,  

The following Metalink note may be of interest to you:  

Refining Remote Archival Over a Slow Network with the ARCH Process   Doc ID: Note:260040.1  

Cheers,  

David Taft

-----Original Message-----

From: Ankur Godambe [mailto:agodambe_at_ketera.com] Sent: Friday, April 06, 2007 4:21 PM
To: oracle-l_at_freelists.org
Subject: arch slow and standby.

        Hi,

        In a 9i managed standby database with primary and secondary in maximum performance mode if arch is not able to archive to remote destination due to n/w issues etc, it will retry archiving to remote destination depending upon REOPEN and MAX_FAILURES parameter. But what if the n/w is slow (not dead and arch is actively archiving redo log) and by the time it's archiving to the remote destination all the log groups on primary are filled and lgwr comes back to the group being archived currently for reuse. Will the database hang? Or it will stop archiving to remote with error message somewhere in dictionary? I tried simulating but since I have the test databases on lan couldn't simulate.

        I think it will wait till it's archived to the remote. Anyone who has faced similar situation or knows what might happen?          

        Thanks,

        Ankur

--

http://www.freelists.org/webpage/oracle-l Received on Tue Apr 10 2007 - 14:02:18 CDT