Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.misc -> Re: TNS Resolve Problem
tomtailor_at_freesurf.fr wrote in
news:1126103012.293349.100830_at_g44g2000cwa.googlegroups.com:
> Hello!
>
> I've installed 10g on XP Prof and before reboot everything worked ok
> sql plus and Webadminconsole. After reboot I'm just able to access
> data via Webclients (Admin or isqlpplus) but I'm not able to access
> via console sqlplus ore ODBC.
>
> What is the Damn Error??
>
> My listerner and tns.oras are:
> D:\oracle\product\10.1.0\db_1\network\admin>type listener.ora
> # listener.ora Network Configuration File:
> D:\oracle\product\10.1.0\db_1\NETWORK
> \ADMIN\listener.ora
> # Generated by Oracle configuration tools.
>
> SID_LIST_LISTENER (SID_LIST (SID_DESC (SID_NAME = KTP)
> )
> )
>
> LISTENER (DESCRIPTION (ADDRESS = (PROTOCOL = TCP)(HOST =
> ci-test.CI_BHG)(PORT = 1521))
> )
>
>
> D:\oracle\product\10.1.0\db_1\network\admin>type tnsnames.ora
> # tnsnames.ora Network Configuration File:
> D:\oracle\product\10.1.0\db_1\NETWORK
> \ADMIN\tnsnames.ora
> # Generated by Oracle configuration tools.
>
> KTP (DESCRIPTION (ADDRESS_LIST (ADDRESS = (PROTOCOL =
> TCP)(HOST = ci-test.CI_BHG)(PORT = 1521))
> )
> (CONNECT_DATA (SERVER = DEDICATED)
> (SERVICE_NAME = KTP)
> )
> )
>
> and the tnsping result is:
> D:\oracle\product\10.1.0\db_1\network\admin>tnsping KTP
>
> TNS Ping Utility for 32-bit Windows: Version 10.1.0.2.0 - Production
> on 07-AUG-2
> 005 16:12:21
>
> Copyright (c) 1997, 2003, Oracle. All rights reserved.
>
> Parameterdateien benutzt:
> D:\oracle\product\10.1.0\db_1\network\admin\sqlnet.ora
>
>
> Adapter TNSNAMES zur Aufl÷sung des Alias benutzt
> Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS
> (PROTOCOL = TCP) (HOST = ci-test.CI_BHG)(PORT = 1521))) (CONNECT_DATA
> = (SERVER DEDICATED) (SER VICE_NAME = KTP)))
> OK (50 ms)
>
> but a connect to sqlplus fails:
> D:\Dokumente und Einstellungen\oracle.CI-TEST>sqlplus sysman/****@KTP
>
> SQL*Plus: Release 10.1.0.2.0 - Production on Sun Aug 7 16:15:18 2005
>
> Copyright (c) 1982, 2004, Oracle. All rights reserved.
>
> ERROR:
> ORA-12154: TNS:could not resolve the connect identifier specified
>
>
> Enter user-name:
>
> Need Help!
>
> THX
> Christian Meier
>
>
12154, 00000, "TNS:could not resolve the connect identifier specified"
// *Cause: A connection to a database or other service was requested using // a connect identifier, and the connect identifier specified could not // be resolved into a connect descriptor using one of the naming methods // configured. For example, if the type of connect identifier used was a // net service name then the net service name could not be found in a // naming method repository, or the repository could not be // located or reached. // *Action: // - If you are using local naming (TNSNAMES.ORA file): // - Make sure that "TNSNAMES" is listed as one of the values of the // NAMES.DIRECTORY_PATH parameter in the Oracle Net profile // (SQLNET.ORA) // - Verify that a TNSNAMES.ORA file exists and is in the proper // directory and is accessible. // - Check that the net service name used as the connect identifier // exists in the TNSNAMES.ORA file. // - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA // file. Look for unmatched parentheses or stray characters. Errors // in a TNSNAMES.ORA file may make it unusable. // - If you are using directory naming: // - Verify that "LDAP" is listed as one of the values of the // NAMES.DIRETORY_PATH parameter in the Oracle Net profile // (SQLNET.ORA). // - Verify that the LDAP directory server is up and that it is // accessible. // - Verify that the net service name or database name used as the // connect identifier is configured in the directory. // - Verify that the default context being used is correct by // specifying a fully qualified net service name or a full LDAP DN // as the connect identifier // - If you are using easy connect naming: // - Verify that "EZCONNECT" is listed as one of the values of the // NAMES.DIRETORY_PATH parameter in the Oracle Net profile // (SQLNET.ORA). // - Make sure the host, port and service name specified // are correct. // - Try enclosing the connect identifier in quote marks. // // See the Oracle Net Services Administrators Guide or the Oracle // operating system specific guide for more information on naming.Received on Wed Sep 07 2005 - 09:36:41 CDT