TNSNAMES defines multiple connect methods, which is used?

From: Jonathan Gennick <gennick_at_worldnet.att.net>
Date: 1998/05/08
Message-ID: <6itq2m$t3r@bgtnsc01.worldnet.att.net>#1/1

I recently setup a new instance on an NT box, and Enterprise Manager generated the following entry in my TNSNAMES file:

PINE.world=(DESCRIPTION=(ADDRESS_LIST =(ADDRESS=(COMMUNITY= NMP.world)(PROTOCOL= NMP)(SERVER= PMA0781D00)(PIPE= ORAPIPE))(ADDRESS=(COMMUNITY= TCP.world)(Host = pma0781d00)(PROTOCOL= TCP)(Port= 1521))(ADDRESS=(COMMUNITY= TCP.world)(Host = 127.0.0.1)(PROTOCOL= TCP)(Port= 1521))(ADDRESS=(COMMUNITY= TCP.world)(Host = pma0781d00)(PROTOCOL= TCP)(Port= 1526))(ADDRESS=(COMMUNITY= SPX.world)(PROTOCOL= SPX)(Service=
pma0781d00_lsnr)))(CONNECT_DATA=(SID=PINE)(SERVER=DEDICATED)))

This entry contains connection information for named pipes, TCP/IP, and SPX. How can that work? How does Oracle choose between NMP, TCP/IP or SPX? I'm used to seeing much simpler entries, like the following:

dev.world =
  (DESCRIPTION =
(ADDRESS_LIST =

        (ADDRESS =
          (PROTOCOL = SPX)
          (Service = oradetroit1)
        )

    )
(CONNECT_DATA =

       (SID = dev)
    )
  )

Should I revise my entry for PINE, and simplify it to look more like that for DEV?

Jonathan Received on Fri May 08 1998 - 00:00:00 CDT