Home » Open Source » Programming Interfaces » Microsoft ODBC for Oracle Can't Find Server
Microsoft ODBC for Oracle Can't Find Server [message #272048] Wed, 03 October 2007 15:04 Go to next message
sbrown1038
Messages: 1
Registered: October 2007
Location: New York
Junior Member
I'm using an application called Integration Manager that used a data source based on the Microsoft ODBC for Oracle driver. Up until we moved the server (running Oracle 7.3) from New Jersey to New York, it was working fine. Now, although I updated the IP address in TNSNAMES.ORA, I get the following error message from the Microsoft ODBC driver:

ORA-12154: TNS:could not resolve the connect identifier specified

Applications using Oracle's ODBC drive work OK. Any help getting the driver to see the server in its new location would be appreciated.
Re: Microsoft ODBC for Oracle Can't Find Server [message #272074 is a reply to message #272048] Wed, 03 October 2007 23:37 Go to previous message
Michel Cadot
Messages: 57617
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.

A solution may be to use the driver that works.

Regards
Michel
Previous Topic: Example of Inserting and Retrieving data from xml file
Next Topic: Oracle and Visual Basic 6.0
Goto Forum:
  


Current Time: Mon Apr 21 10:06:45 CDT 2014

Total time taken to generate the page: 0.08532 seconds