This content has been marked as final. Show 3 replies
You can say LNS process is in wait state to the value set in NET_TIMEOUT.
1) The LNS process will remain in a wait state till the NET_TIMEOUT. Right?
Redo Transport Session to the Standby database is terminated.
2) If the network between primary & standby is not re-established within NET_TIMEOUT, will the primary database be shutdown after NET_TIMEOUT period?
Edited by: Sunny kichloo on Apr 9, 2013 12:06 AM
Hii Sunny kichloo
Thanks for your valuable response and link. I have gone through the link you provided.
As per oracle doc "If an acknowledgement is not received within NET_TIMEOUT seconds, an error is logged and the redo transport session to that destination is terminated."
In response to 2nd answer. I have couple of questions
If an acknowledgement from RFS is not back to LNS due to network down, LGWR cannot send a commit acknowledgment to the user and the commit operation of the primary database is held up.
1) If the DB is in Max Performance mode will it freeze until the network problem is solved?
2) If the DB is in Max Protection mode will it freeze or will it shutdown?
If you have set Maximum Protection, you have chosen a configuration that guarantees that no data loss will occur. You have set this up by specifying the LWGR, SYNC, and AFFIRM attributes of the LOG_ARCHIVE_DEST_n parameter for at least one standby database. This mode provides the highest level of data protection possible and to achieve this the redo data needed to reocver each transaction must be written to both the local online redo log and the standby redo log on at least one standby database before the transaction commits. To ensure data loss cannot occur, the primary database shuts down if a fault (such as the network going down) prevents it from writing its redo stream to at least one remote standby redo log.
If the DB is in Max Protection mode will it freeze or will it shutdown?