Re: Routing question.

All depends on whether you're using DNS, and if both IP's are listed for that host in DNS (round-robin).

If you want the listener to bind to both IP's and both IP's are listed in DNS, then listener.ora needs to have both IP's, not DNS name. Otherwise the listener binds only to the first IP returned by DNS.

Then, when the listener is bound to both IP's, tnsnames.ora would have DNS name.

• listener.ora LSNR01 = (ADDRESS_LIST = (ADDRESS= (PROTOCOL= IPC)(KEY=lsnr01)) (ADDRESS= (PROTOCOL= TCP)(Host= ###.###.##.#01)(Port= 1521)) (ADDRESS= (PROTOCOL= TCP)(Host= ###.###.##.#02)(Port= 1521)) )
• tnsnames.ora orcl01 = (DESCRIPTION = (ADDRESS = (PROTOCOL=TCP)(HOST=host.domain)(PORT=1521)) (CONNECT_DATA = (SID =orcl01)) )

"Ferguson II, Roy E" wrote:
>
> All,
>
> Can you bind Oracle to communicate through a particular IP address by making
> note of it in the tnsnames.ora and listener.ora files.
>
> or does it use the operating system for routing?
>
> We are adding a second nic card for redundancy purposes whereby if one NIC
> is down, the other NIC would pick up the load.
>
> Environment:
> Sun Solaris
> Oracle EE 8.1.7.2
>
> The current game plan is documented below:
> -------------------------
> Configure the interface on the sun server
> * ping from local machine to the new address
> * ping from other machine on the same subnet to new address
>
> Add a second ADDRESS= line to ADDRESS_LIST section in listener.ora file
> * manually tnsping on db server using:
> tnsping "(ADDRESS=(PROTOCOL=TCP)(HOST=new.ip.address)(PORT=1521))"
> * manually tnsping from other machine using same command
>
> Add second address to address tnsnames.ora service name (under
> ADDRESS_LIST section)
> * tnsping the service name to ensure that some form of it works (this
> will not check the new interface, necessarily)
> * use sqlplus to connect to service
>
> Add second address to clients' tnsnames.ora files
> * tnsping service name on each client
> * use sqlplus to connect to service on each client
>
> Physically remove ethernet cable from old NIC on DB server (could be
> simulated by simply bringing down the network interface in software, but
> this could cause other problems)
> * tnsping service name from db server
> * tnsping service name from clients
> * use sqlplus to connect to service on db server
> * use sqlplus to connect to service on each client
>
> Replace network cable and/or re-enable interface on db server
> * tnsping service name from db server
> * tnsping service name from clients
> * use sqlplus to connect to service on db server
> * use sqlplus to connect to service on each client
>
> Thanks in advance.
>
> Roy E Ferguson II
>
> --
> Please see the official ORACLE-L FAQ: http://www.orafaq.com
> --
> Author: Ferguson II, Roy E
> INET: roy.e.ferguson.ii_at_intel.com
>
> Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> San Diego, California -- Public Internet access / Mailing Lists
> --------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
> (or the name of mailing list you want to be removed from). You may
> also send the HELP command for other information (like subscribing).

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Suzy Vordos
  INET: lvordos_at_qwest.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).