Shulou(Shulou.com)05/31 Report--

This article introduces the relevant knowledge of "how to understand the FAL_SERVER parameters in the database". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

FAL_SERVER parameter explanation:

1. If the network is delayed or resources are insufficient, there will be a gap between primary and standby, resulting in some archive logs not being transmitted in time and applied to the standby library.

two。 Because MRP (managed recovery process) / LSP (logical standby process) does not have the ability to communicate directly with primary to obtain lost archive logs. 3. So these gaps are solved by the FAL server, and the FAL_SERVER is defined by the initialization parameters.

4. Set FAL_SERVER to the TNS service name of the slave database.

> main library: FAL_SERVER=PROD1 slave library: FAL_SERVER=SBDB1

Restart the database to make the parameters take effect. Although the modification of this parameter does not require a restart of the database, when running SWITCHOVER, it is found that if you do not restart the data library, Oracle does not re-obtain the value of FAL_SERVER, but according to the value of FAL_SERVER loaded at this startup.

This is the end of the content of "how to understand FAL_SERVER parameters in the database". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.