RAC Local_listener, an Oracle Appendix

RAC Local_listener, an Oracle appendix first a conversation: www.2cto.com cainiao asked: I set local_listener = 'listener1' In the parameter file, and then start the database to report an error. SQL> startup ORA-00119: invalid specification for system parameter LOCAL_LISTENER ORA-00132: syntax error or unresolved network name 'listener1' syntax incorrect? Www.2cto.com old bird back: tnsnames to be on the server. set in ora to map listener1 like this: listener1 = (ADDRESS = (PROTOCOL = TCP) (HOST = virtual ip) (PORT = 1521) or you can directly set it like this: local_listener = '(ADDRESS = (PROTOCOL = TCP) (HOST = virtual ip) (PORT = 1521)' cainiao looks confused and weak: in this case, listener1 is the default listener? Or tell pmon to register the registration information to listener1? Old bird returned: pmon registered cainiao a little clear, and asked: Thank you! After the database is added, you can start the database, but you do not understand how the database is operated internally. Please advise. why can it be started after the database is added? Old bird: because it will go to the server's tnsnames. ora Find ah, can not find of course parsing can not ah, and then the error: ORA-00132: syntax error or unresolved network name 'listener1' In the RAC environment, client connection, sometimes receive ORA-12545: because the target host or object does not exist, the troubleshooting method for connection failure is the same... The story is called here, And Local_listener has two functions: ● PMON dynamic registration of non-standard ports Dynamic Registration default Oracle can only register port 1521, if your port is 1522 or other, oracle cannot know, so you only need to tell ORACLE Local_listener. ● rac server Load balancer has two types of rac server Load balancer: CLIENT and SERVER. in ora, The LOAD_BALANCE = yes parameter is configured based on the number of connections, or the probability to connect to Oracle may not cause errors if it is not configured. Another case is that the Local_listener can be used because Oracle will detect SERVER load, when a process enters one of the nodes, if the local node is not connected to the server, it will detect the node with low load. If the local node is connected directly through Local_listener For other machines, since Oracle does not know how to configure other nodes, Remote_listener can be used to configure local_listener: ① In listener. set the listening port [plain] Think = (description = (address = (protocol = tcp) (host = loveoracle) (port = 1522) in ora ))) lsnrctl start Think start listener ② In tnsname. set net service name [plain] Think = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = loveoracle) (PORT = 1522) in ora ))) (CONNECT_DATA = (service_name = or Cl) ③ then you can set local_listener alter system set local_listener = Think; ④ register listener alter system register with the database; in fact, Local_listener is set to solve a BUG → it is mainly the VIP. This is the appendix of Oracle and will be cut out sooner or later! In my environment, many times I have not set Local_listener. Even if I want to write it, it is also the VIP address written. This is true for 10g and 11g.