Oracle: why do I have to append .world to tnsname in tnsnames.ora?
October 08, 2008 19:33:21 Last update: October 08, 2008 20:17:42
In
To force a lookup without
sqlnet.ora, there's a parameter named NAMES.DEFAULT_DOMAIN that usually contains the value world. If you remove this parameter then you don't need to append .world. My sqlnet.ora contains three lines:
# sqlnet.ora Network Configuration File: C:\work\globaltnsnames\sqlnet.ora # Generated by Oracle configuration tools. # Use the parameter SQLNET.AUTHENTICATION_SERVICES to enable one or more authentication services. # Possible values are (among other valid ones): # 1. none - use a valid username and password to access the database # 2. all - for all authentication methods # 3. nts - use Windows NT native authentication SQLNET.AUTHENTICATION_SERVICES= (NTS) # Use the parameter NAMES.DIRECTORY_PATH to specify the order of the naming methods used for # client name resolution lookups. # 1. LDAP - resolve database service (net service) name through a directory server # 2. TNSNAMES - resolve a net service name through the tnsnames.ora file on the client # 3. EZCONNECT/HOSTNAME - elect to enable clients to use a TCP/IP connect identifier, consisting of # a host name and optional port and service name. # 4. ONAMES - Oracle Names Server, which is no longer available for Oracle 10g and above. NAMES.DIRECTORY_PATH= (LDAP, TNSNAMES, EZCONNECT, ONAMES, HOSTNAME) # Use the parameter NAMES.DEFAULT_DOMAIN to set the domain from which the client most often looks # up names resolution requests. When this parameter is set, the default domain name is automatically # appended to any unqualified net service name or service name. NAMES.DEFAULT_DOMAIN = world
To force a lookup without
NAMES.DEFAULT_DOMAIN appended, append a dot to the tnsname:
tnsping unqualified_tnsname_name.