How+to+Configure+A+Second+Listener+on+a+Separate+Network+in+11.2+Grid+Infrastructure+(文档+ID+1063571.1)

1、How to Configure A Second Listener on a Separate Network in 11.2 Grid Infrastructure (文档 ID 1063571.1)转到底部In this DocumentGoalSolutionReferencesApplies to: Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and laterOracle Database Exa

2、data Cloud Machine - Version N/A and laterOracle Cloud Infrastructure - Database Service - Version N/A and laterOracle Database Backup Service - Version N/A and laterInformation in this document applies to any platform.GoalDuring the Grid Infrastructure installation, the (default) node VIP listener

3、is always created referencing the public network. However, some systems may be attached to more than 1 public network, so there may be a need to create a second listener for this second public network. The purpose of this note is to explain how to add/create/configure a second listener on a second n

4、etwork in an 11.2 Grid Infrastructure environment.This note does not apply to the binding of two public network interfaces for failover purposes, like IPMP or bonding etc.SolutionAssume the following names are defined for two nodes cluster (DNS or /etc/hosts):# public host name and associated VIP on

5、 eth1<racnode1>             10.x.x.1<racnode1>-vip         10.x.x.11<racnode2>             10.x.x.2<racnode2>-vip         10.x

6、.x.22# scan name#racscan>              10.x.x.41#                     10.x.x.42#                     10.x.x.43 # host name for the 2nd public netwo

7、rk and associated VIP on eth2<node1n2>              20.x.x.1<node1n2>-vip          20.x.x11<node2n2>              20.x.x.2<node2n2>-vip    &#

8、160;     20.x.x.22  A listener has already been created on 10.10.10.x network, we are going to create a 2nd listener on 20.20.20.x network.1. Ensure a VIP address is defined for the 2nd public networkIn this example it's <node1n2>-vip and <node2n2>-vip (see a

9、bove).2. Create the CRS resource for the 2nd networkA new network and new vip resources for the 2nd network are created by using the '-k' switch (Please note: the <node_name> should be supplied in lowercase):as root user:# srvctl add vip -n <node_name> -k <network_number> -

10、A <name|ip>/<netmask>/if1|if2. -veg:# srvctl add vip -n <racnode1> -k 2 -A 20.x.x.11/255.255.255.0/eth2# srvctl add vip -n <racnode2> -k 2 -A 20.x.x.22/255.255.255.0/eth2This command will implicitly create the dependent network resource.From 11.2.0.2+, network resou

11、rce can be created explicitly:as root user:# srvctl add network -k <net_num> -S <subnet>/<netmask>/if1|if2. -w <network_type> -veg:# srvctl add network -k 2 -S 20.x.x.0/255.255.255.0/eth2Then add vip resource for the 2nd network:# srvctl add vip -n <racnode1> -k 2

12、-A 20.x.x.11/255.255.255.0/eth2# srvctl add vip -n <racnode2> -k 2 -A 20.x.x.22/255.255.255.0/eth2The CRS resource 'work' and 2nd network vip should now have been created, they are both required for the 2nd listener, run the following command to verify:# crsctl stat res -t |grep -

13、E 'net|vip'workworkora.<racnode1>.vipora.<node1n2>-vip.vipora.<racnode2>.vipora.<node2n2>-vip.vip.3. Create a new RAC listener using 'netca'As the grid user invoke "netca" from the 11.2 GRID_HOME, the select "Listener configuration" -> &

14、quot;Add", enter Listener name as required.  For example: "LISTENER_2". On the next page, "Select Subnet",  the 2nd subnet will appear in the drop down list. For example:2 20.x.x.0/255.255.255.01 10.x.x.0/255.255.255.0Select subnet 2 , select the protocol and defin

15、e the Listener port as desired to complete the listener creation.Note: When adding 2nd listener with srvctl on the same port, it may fail with:$ ./srvctl add listener -l <LISTENER_2> -p 1521 -k 2PRCN-2061 : Failed to add listener ora.<LISTENER_2>.lsnrPRCN-2065 : Port(s) 1521 are not avai

16、lable on the nodes givenPRCN-2067 : Port 1521 is not available across node(s) "<racnode1>"The workaround is to use "-s" option:$ ./srvctl add listener -l <LISTENER_2> -s -p 1521 -k 24. Verify the new RAC listenerThe new listener will be started at the end of netca. Th

17、is listener will listen on the IP address 20.20.20.11 (or 20.20.20.22 for node 2) associated with the 2nd network.  To check:$ lsnrctl status <listener_2>LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 08-FEB-2010 16:10:23Copyright (c) 1991, 2009, Oracle. All rights reserved.Connect

18、ing to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=<LISTENER_2>)STATUS of the LISTENER-Alias <LISTENER_2>Version TNSLSNR for Linux: Version 11.2.0.1.0 - ProductionStart Date 08-FEB-2010 16:10:20Uptime 0 days 0 hr. 0 min. 2 secTrace Level offSecurity ON: Local OS AuthenticationSNMP OFFListen

19、er Parameter File /u02/app/11.2.0/grid/network/admin/listener.oraListener Log File /u02/app/oragrid/diag/tnslsnr/<racnode1>/<listener_2>/alert/log.xmlListening Endpoints Summary.(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=<LISTENER_2>)(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.x.x.1

20、)(PORT=1588)(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=20.x.x.11)(PORT=1588)The listener supports no servicesThe command completed successfully Please note the output for 11.2.0.2+ only shows two ADDRESS lists:(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=<LISTENER_2>)(DESCRIPTION=(ADDRESS=(PRO

21、TOCOL=tcp)(HOST=20.x.x.11)(PORT=1588)5. Prepare the database instance for the new listenerTo ensure that connections to the remote listener are only redirected to the local listener on the same network, LISTENER_NETWORKS parameter needs to be set in the pfile or spfile for the database instance.Assu

22、ming the RDBMS $ORACLE_HOME/network/admin/tnsnames.ora (or the $TNS_ADMIN/tnsnames.ora) has the following local and remote listener defined,  prepare similar content for each node using node specific VIP name (or VIP IP adddress). For example, on node1:<listener_1> =   (DESCRIPT

23、ION =     (ADDRESS = (PROTOCOL = TCP)(HOST = <racnode1>-vip)(PORT = 1521)   )<listener_2> =   (DESCRIPTION =     (ADDRESS = (PROTOCOL = TCP)(HOST = 20.X.X.11)(PORT = 1588)   )<remote_2> =   (DESCRIPTION

24、_LIST =     (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 20.x.x.11)(PORT = 1588)     (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 20.x.x.22)(PORT = 1588)   )On node 2:<listener_1> =   (DESCRIPTION =    &#

25、160; (ADDRESS = (PROTOCOL = TCP)(HOST = <racnode2>-vip)(PORT = 1521)   )<listener_2> =   (DESCRIPTION =      (ADDRESS = (PROTOCOL = TCP)(HOST = 20.x.x.22)(PORT = 1588)   )<remote_2> =   (DESCRIPTION_LIST =  

26、   (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 20.x.x.11)(PORT = 1588)     (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 20.x.x.22)(PORT = 1588)   )The database parameter LISTENER_NETWORKS needs to be set to include both default network and the 2nd n

27、etwork information:alter system set LISTENER_NETWORKS='(NAME=<network1>)(LOCAL_LISTENER=<listener_1>)(REMOTE_LISTENER=<remote_2>)','(NAME=<network2>)(LOCAL_LISTENER=<listener_2>)(REMOTE_LISTENER=<remote_2>)' scope=both sid='<SID>'local_listener and remote_listener parameters should not be set if included in above. Above setting is pe