Re: ORA-12154: TNS: could not resolve service name
Date: 1996/08/25
Message-ID: <4vqvgq$t65_at_cyber2.servtech.com>#1/1
In <4vmqpd$led_at_qualcuno.nettuno.it> imola01_at_imola.nettuno.it (Massimo Ferrari) writes:
>peng_at_infinite.cs.swt.edu (Wuxu Peng) wrote:
>>I am in the process of installing Unix (Digital) Server/Client
>>based Oracle pacakge. The command "sqlplus SCOTT/TIGER" was
>>successful on the server machine. But, testing "sqlplus
>>SCOTT/TIGER_at_comets", where 'comets' is the server aliase, or
>>doing anything like "sqlplus oracle/password_at_comets",
>>from either the server or clients, would result in above error
>>message. Helps are appreciated.
>comets must be a database link created with
>create database link comets
>connect to yyyy identified by xxxxx
>using 'T:ipaddressHost:oraSid'
That works for SQL*Net V1, but not V2.
For SQL*Net V2 (where you would create the link as:
create database link comets connect to yyyy identified by xxxxx using 'tns_entry'; )
you then CANNOT use "sqlplus oracle/password_at_comets". You must use the "tns_entry" instead: "sqlplus oracle/password_at_tns_entry". This will work just fine.
BTW, for clarity sake, we name our TNS entries as "ipaddressHost_oraSid", so they are similar to the SQL*Net V1 format, and just as informative. Note that we use host names, not IP addresses.
-- ------------------------------------------------------------------------------ Computer General Rochester, NY (716) 436-6372 "... providing general computer solutions to specific business problems" gwn_at_servtech.comReceived on Sun Aug 25 1996 - 00:00:00 CEST