Re: SQL Net 2 problems

From: Radojevic <gradojev_at_us.oracle.com>
Date: 1996/11/23
Message-ID: <575ph5$54f_at_inet-nntp-gw-1.us.oracle.com>#1/1


        The most common reason for getting an ora-12154 eventhough you've got the correct servicename (alias) defined in the tnsnames.ora file is this: you enter a sqlnet v2 connect string, like this:

sqlplus scott/tiger_at_my_v2_servicename

        However, your sqlnet.ora file has entries in it, like this:

names.default_domain = world
name.default_zone = world

        sqlplus will see you have not supplied a domain at the end of your sqlnet v2 servicename, so it will happily append the one defined in your sqlnet.ora for you. So, your connect string ends up being executed, like this:

sqlplus scott/tiger_at_my_v2_servicename.world

        sqlplus looks for my_v2_servicename.world in your tnsnames.ora file, but doesn't find it, so it returns an ora-12154.

        In this case, you can either comment out the names.default_domain and name.default_zone parameters from sqlnet.ora and not use domains, or append a domain to the end of your tnsnames.ora servicename entries and use the full servicename.domain connect string.

             g

////////////////////////////////////////////////////////////////////

/ Oracle Networking Support / guru dude, joe SQL*Net, joe SQL*Toes /
/ Oracle RDBMS Support / process evangelist /
////////////////////////////////////////////////////////////////////
Received on Sat Nov 23 1996 - 00:00:00 CET

Original text of this message