Global_name issue + connection using TNS -trouble

Question

IPT_TEST.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 172.29.62.21)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = TEST)
IPT_TEST =
*(DESCRIPTION =*
*(ADDRESS_LIST =*
*(ADDRESS = (PROTOCOL = TCP)(HOST = 172.29.62.21)(PORT = 1521))*
*(CONNECT_DATA =*
*(SERVICE_NAME = TEST.IP-TECH.COM)*
Now the Global_Name of the database is
select * from global_name
TEST.IP-TECH.COM
but by SQLDeveloper I am able to connect to TEST SID. But SQLDeveloper uses JDBC connection not TNS.
But while am trying using TNS , am not being able to connect to TEST.IP-TECH.COM ,
Even while am trying to configure Net Configuration Assisstant , it is not recognising TEST.IP-TECH.COM as a valid service name.
Also, I tnspinged. That is working. :(
C:\Documents and Settings\272318>tnsping 172.29.62.21
TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 22-JUL-2
*011 13:00:11*
Copyright (c) 1997, 2005, Oracle.  All rights reserved.
Used parameter files:
D:\oracle\product\10.2.0\client_3\network\admin\sqlnet.ora
Used EZCONNECT adapter to resolve the alias
Attempting to contact (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=172.29.62.21))(AD
DRESS=(PROTOCOL=TCP)(HOST=172.29.62.21)(PORT=1521)))
OK (500 msec)
Edited by: :) on Jul 22, 2011 1:00 PM

Answer 1

:) wrote:
Oh very Sorry, actually I thought I went angry probably my question is so easy.
Yes I know that SQL Server can also use TNS.But currently, it's not connecting by TNS, it's using the JDBC connection
ORA-12154 error is the one I am getting.
Ok, then after I login in my onsite server will ping the service name "TEST" and will let you know the result.
My senior told me to check in the serve
Select * from gv$active_services;
I will request my onsite counterpart to check that also.You are free to rant what ever nonsense you believe.
ORA-12154 mean the lookup on the client failed & has NOTHING to do with anything on DB Server
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.