TNS_ADMIN is useful if you have multiple homes but want to maintain only a single set of network configuration files. With local naming, you will have a tnsnames.ora file either in your Oracle home: $ORACLE_HOME/network/adminĭirectory, or if using read only homes, you may find it here: $ORACLE_BASE_HOME/network/adminĪlternately you may have a TNS_ADMIN environment variable telling your client to look in another location. In many cases you will also need to know the port and service if defaults are not in use on the target host. Rather, you must already know the target host. There is a fourth connection method: Easy Connect, but it is not a name-lookup methodology. using a third party NIS (this is uncommon) Within name lookup there are 3 options only two of which are in common usage. The functionality breaks down into two components – name lookup and pinging the listener at a host/port combination found in a TNS descriptor. Developers using jdbc thin clients may also miss having this handy tool at their disposal.įortunately there are ways to replicate some of the functionality of TNSPING using other tools. While the Instant Client is a popular client installation for many applications, very often developers and admins become frustrated by the conspicuous absence of the TNSPING utility.
0 Comments
Leave a Reply. |