Home » Open Source » Programming Interfaces » ORA- 12154: TNS couldn't resolved name (oracle 9i R2)
ORA- 12154: TNS couldn't resolved name [message #324126] Sat, 31 May 2008 00:18 Go to next message
poratips
Messages: 345
Registered: April 2005
Location: IL
Senior Member
Hi,
I am getting ORA-12154 error while trying to connect sql*plus or TOAD, even OWM too.
We have just changed IP address and i am in all trouble to connect.
Could you please help me out for to resolve this issue?
I have multiple home like ora9i, ora92, ora81 and Ora6i.
It was working fine till point but its throwing me error now.
I tried to replace the new ip address and also tried with actual host/server name but no luck.

Thanks,
poratips
Re: ORA- 12154: TNS couldn't resolved name [message #324156 is a reply to message #324126] Sat, 31 May 2008 03:45 Go to previous messageGo to next message
Michel Cadot
Messages: 68624
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
]
ORA-12154: 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.

Regards
Michel
Re: ORA- 12154: TNS couldn't resolved name [message #325213 is a reply to message #324126] Thu, 05 June 2008 05:25 Go to previous messageGo to next message
adzikiewicz
Messages: 3
Registered: June 2008
Junior Member
This happen to us when we change the hosts file from say
12.12.12.12 localhost to 12.12.12.12 oracleserver.

The tnsnames file had 'localhost' in it. This was a Linux server.

Anthony
Re: ORA- 12154: TNS couldn't resolved name [message #325216 is a reply to message #325213] Thu, 05 June 2008 05:31 Go to previous message
Michel Cadot
Messages: 68624
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
If you change the name, change tnsnames entry.

Regards
Michel
Previous Topic: Need information for Transparent Gateway for SQL Server
Next Topic: Store Picture in Oracle with VB 6.0 Interface
Goto Forum:
  


Current Time: Thu Mar 28 07:04:27 CDT 2024