Home » RDBMS Server » Server Administration » TNS 11254 error (10.2.0.1, Windows 2003)
TNS 11254 error [message #351874] Fri, 03 October 2008 09:33 Go to next message
sant_new
Messages: 165
Registered: June 2008
Senior Member
Hi all,

One of our client is trying to connect to our database from his local pc. We are able to connect to the database fine from here.
But when he connects from his pc via vpn it gives him this error:

Ora-12154: TNS:could not resolve the connect identifier specified.

I checked the path and the Oracle client is in the path on his pc. Tnsping works. Not sure what else I should check. I do not have access to his pc, I just have to troubleshoot on the phont.

Below is his sqlnet.ora and tnsnames.ora.

# SQLNET.ORA Network Configuration File: C:\oracle\product\10.2.0\client_1\network\admin\sqlnet.ora


#NAMES.DIRECTORY_PATH= (TNSNAMES)


# tnsnames.ora Network Configuration File: C:\oracle\product\10.2.0\client_1\NETWORK\ADMIN\tnsnames.ora
# Generated by Oracle configuration tools.

alp =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = alm)(PORT = 1525))
    )
    (CONNECT_DATA =
      (SID = alp)
      (SERVER = DEDICATED)
    )
  )


Please give me your suggestions.
Thanks.

[Updated on: Fri, 03 October 2008 09:56]

Report message to a moderator

Re: TNS 11254 error [message #351880 is a reply to message #351874] Fri, 03 October 2008 10:10 Go to previous message
Michel Cadot
Messages: 64103
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
Previous Topic: Safely remove OCM (ORACLE_OCM) after applying patch set 3
Next Topic: ORA-00600 Error in Alert Log
Goto Forum:
  


Current Time: Sun Dec 04 04:21:33 CST 2016

Total time taken to generate the page: 0.26689 seconds