Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.6K 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.9K 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
- 395 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
Where ODBC Connector is defined in Windows registry?

Good day!
I have an app which use ODBC Connector, and it don't works as well. When I trying to access ODBC programmatically, I get an error from ODBC Driver Manager, smth like: " Data source not found and no driver specified, the default "
(my OS language is different, so it's not verbatim).
I changed MySQL ODBC Connector many times, I tried different versions and tried specify driver in registry manualy (in branch HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI). Also, I had tried to track how does it work step by step, and I stop at odbc32.dll. As I think it is ODBC Driver Manager which can't find smth necessary, but what?
Answers
-
Hi,
If you have installed the Oracle Client/ODBC driver, then please create a Data Source Name (DSN) in ODBC data source administrator.
Once the DSN is created successfully (along with Test Connection), refer the DSN.
Then you will resolve the above error message.
thanks and regards
Venkat