This content has been marked as final. Show 3 replies
You can monitor a resolve a gap without these parameters. Manually for example.
Can Gap detection and resolution be possible without setting FAL_server or FAL_Client on the the standby? (Version 10.2.0.4 & 126.96.36.199)
Use a query like this to check :
On the Primary LNS collects redo data from the online redo log files. The log writer process never waits for the LNSn for any reason in release 10.2. But in I believe in 11 if you use SYNC LGWR will wait for acknowledgement from the LNS before telling the client a commit has occurred.
Is there any relationship between LGWR & LNS?
Oracle 10 is pretty old at this point and I cannot tell details without referring to the Oracle docs.
The LGWR process can be used to transmit redo data to remote destinations.
The biggest impact is your Standby database is not ready for Primary mode. The NOARCHIVELOG question has come here 3 times in the past week. My question is what advantage is this? A Standby mode database applies Archive from a Primary. If this leaves a copy on the Standby you can clean it up as soon as it applied using several well documented methods.
What impact does NOARCHIVELOG mode have on standby database?
1)if you don't set the two parameters , you should observe by yourself when archive log gap occurs , then copy archive log gap to the standby database and register them.
2)just like mseberg said .
3) i think it must impact standby database .
From Document : 6.3 Applying Redo Data to Physical Standby Databases | http://docs.oracle.com/cd/B19306_01/server.102/b14239/log_apply.htm#i1020855
look at the following statement :
By default, the redo data is applied from archived redo log files.
If NOARCHIVELOG mode have on standby database , where archived redo log files come from ?