arch slow and standby.
- From: "Vaidya, Shreepad" <Shreepad.Vaidya@xxxxxxxxxxx>
- To: "'agodambe@xxxxxxxxxx'" <agodambe@xxxxxxxxxx>, oracle-l@xxxxxxxxxxxxx
- Date: Sun, 8 Apr 2007 02:31:20 -0500
Hi Ankur,
In Maximum performance mode "A primary database transaction will not wait to
commit until the redo data needed to recover that transaction is written to
a standby database". In the scenario that you have mentioned
1) Archiving will complete locally and the arch process will then
transfer the archive log to standby database.(ASYNC transfer)
2) On a slow connection the transfer speed will be slow. If a gap is
generated due to this slow connection the gap resolution will come into
picture.
The database will continue working and will not hang
Thanks and regards
Shreepad Vaidya
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Ankur Godambe
Sent: Saturday, April 07, 2007 1:51 AM
To: oracle-l@xxxxxxxxxxxxx
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
Other related posts:
