Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.5K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.8K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 394 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
ODBC Connectivity Issue
We connect fine to another Oracle database via DSN.
However, when attempting to connect to a different database using a Driver={} and a dbq="" reference to specify the service name (which matches in tnsnames.ora),
the ODBC Dialog Box appears and challenges the credentials. A retry results in an ORA 12154 error : "TNS Could not resolve the connect identifier specified".
The credentials work fine when accessing the database via SQL Developer. However, that connection is a BASIC one.
When I select TNS as the connection type and use the TNS, that connection fails when being tested.
The behavior hints at ODBC driver issues. What is missing here ? Does the connecting workstation need a tsnames.ora file entry ?
Answers
-
I think I figured this out. it was the tsnames.ora file.
It didn't have the new database as an entry.
What was really strange about this: we added a System DSN but never referenced it in the connection string.
As long as the DBQ=Service Name reference was used, the connection worked fine.
I asked my manager about tsnames.ora and how it was being maintained. He said "thru LDAP".
Hmmm.....apparently, that sync mechanism is not working well at all.