Oracle Client Odbc Driver

Oracle Client Odbc Driver 9,4/10 9984 reviews
Active3 years, 2 months ago

Devart ODBC Driver for Oracle provides a high-performance and feature-rich connectivity solution for ODBC-based applications to access Oracle databases from Windows, macOS, Linux, both 32-bit and 64-bit. Full support for standard ODBC API functions and data types implemented in our driver makes interaction of your database applications with. It does not work with the more up-to-date native Oracle ODBC driver. I have installed the Oracle Instant Client (32-bit and 64-bit versions on my 64-bit Win 7 PC), each into different ORACLEHOME directories. However when I try to connect via ODBC with Microsoft's driver, I get the error: The Oracle(tm) client and networking components were not. Jan 09, 2019  Hello everyone, welcome to my blog. In this article, I am going to show you how to install Oracle ODBC Driver on Windows 10. I have a working Oracle Database 12c on another computer on my home network. I am trying to connect to my Oracle database. Dec 17, 2012  One fairly common idea is that a 'odbc driver' is standalone, which is wrong. Database client stack is in general required for the ODBC driver to use - think of it as sitting at the application layer. Then the 'end' application is a layer on top. That's one reason to. Step by step instruction how to download and install the ODBC drivers for Oracle 11g release 2. Call 'c: windows SysWOW64 odbcad32.exe' from the start/run box or from the command prompt, so the drivers are more likely to appear. I´ve been through similar problems with Oracle Instant Client (basic and ODBC) 32-bit driver not appearing at the ODBC Admin Window.

I have an old 32-bit software program that connects to an Oracle database but only works with the Microsoft ODBC driver for Oracle. It does not work with the more up-to-date native Oracle ODBC driver.

I have installed the Oracle Instant Client (32-bit and 64-bit versions on my 64-bit Win 7 PC), each into different ORACLE_HOME directories.

However when I try to connect via ODBC with Microsoft's driver, I get the error:

The Oracle(tm) client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3 (or greater) client software installation.

You will be unable to use this driver until these components have been installed.

I can connect to the database fine with Oracle's ODBC driver so the install seems fine, but alas this program will only work with Microsoft's ODBC driver.

Since the Microsoft ODBC driver is apparently unable to find the Oracle Instant Client install, how should I tell it where to look?

Burgi
4,57010 gold badges29 silver badges45 bronze badges
MalvineousMalvineous
1,6912 gold badges14 silver badges29 bronze badges

2 Answers

Technology used: Windows 7, UFT 32 bit, Data Source ODBC pointing out to 32 bit C:WindowsSystem32odbcad32.exe, Oracle client with both versions installed 32 bit and 64 bit.

What worked for me: Easy recovery essentials windows 10 free.

  1. Start -> search for “Edit the system environment variables”
  2. System Variables -> Edit Path
  3. Place the path for Oracle client 32 bit in front of the path for Oracle Client 64 bit. Ex:

techraf
4,28811 gold badges19 silver badges33 bronze badges
AutoDevAutoDev

Turns out this is quite simple. You have to set the PATH environment variable to point to the ORACLE_HOME that you want to use.

For me, I edited the PATH to add ;C:oracleinstantclient32_12_1 on the end and it worked perfectly, no restart needed.

For clarification, the C:oracleinstantclient32_12_1 directory I specified contains files like oci.dll and ociw32.dll and belonged to the 32-bit Instant Client install. I guess it doesn't matter for 64-bit, since there is no Microsoft ODBC 64-bit client.

MalvineousMalvineous
1,6912 gold badges14 silver badges29 bronze badges

Not the answer you're looking for? Browse other questions tagged windows-7databaseodbc or ask your own question.

I recently had an issue where after the installation of a Third party Client side tools, we were not able view the drivers listed in the ODBC Data Source Administrator (odbcad32.exe).

In order to create a DSN to use this third party driver, we had to take a backup/export of the registry key of an existing DSN, edit the content of the registry and rename the existing DSN name to new DSN and then had to merge it back to the registry.

We did check that we had the sufficient privileges on the system, the third party client tools is properly installed and we are able to use this driver for connecting to the third party databases without any issues. So we realized that the issue is not with the third party driver rather it is the registry key from where the ODBC Data Source Administrator (ODBCAD32.exe) actually picks up the list of drivers.

The ODBC Data Source Administrator (ODBCAD32.exe) picks up the list of entries from the following registry path.

On a x64 bit system for a x64 bit drivers: HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INIODBC Drivers

On a x64 bit system for a x32 bit drivers: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBCINST.INIODBC Drivers

On a x32 bit system:

HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INIODBC Drivers

Odbc Driver For Oracle

Note: Above screenshot is taken from a x64 bit system for a x64 bit driver

We realized that the values for the following registry keys should always be (value not set) and if the value is set to an empty string or any other value (either by Third party application or open this registry and close it without any changes) we will run into similar kind of issues where the drivers are not listed in ODBC Data Source Administrator (odbcad32)

On a x64 bit system for a x64 bit drivers:

1) HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INIODBC Drivers(Default) and

2) HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INI(Default)

On a x64 bit system for a x32 bit drivers:

1) HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBCINST.INIODBC Drivers(Default) and

2) HKEY_LOCAL_MACHINESOFTWAREWow6432NodeODBCODBCINST.INI(Default)

On a x32 bit system:

1) HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INIODBC Drivers(Default) and

2) HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INI(Default)

So in order to make this change we would need to perform the following registry changes.

1. Please note before modifying any registry entries we would recommend you to perform a backup of the registry. Please refer the following article on how to backup and restore the registry.

How to back up and restore the registry in Windows: http://support.microsoft.com/default.aspx?scid=kb;EN-US;322756

  1. Login using an administrator account and bring up the registry editor.

a. On Windows Vista and later - Go to Start Run and enter the following: regedit

Best free font manager for mac 2019. The font viewer and any text application without Open Type support only show a Latin Humanist book hand from 1480; when Stylistic Set 19 is on, the Greek characters are inserted typing phonetically on the latin keyboard ( or for eta, u, or y for ypsilon, w or for omega, ch or kh for chi, ph for phi, ps for psi, th for theta). If, in addition, the discretional ligatures are activated, spirits and accents can be inserted typing numbers after the main character; for example, a1 = alpha acute. Humanistic Greek hand from Homer, Ilias, Vatican Library, Cod. 246, written by the Peloponnese Matthaios Lampudes, called Sebastos, undated. The codes are 1 acute, 2 gravis, 3 circumflex, 4 iota sub- or adscriptum, 5 short vowel, 6 long vowel, 7 tonos, 8 spiritus asper, 9 spiritus lenis, 0 dieresis.

Click OK and the Registry Editor will open.

b. On prior versions of Windows

Start > Run > type Regedit.exe and press Enter or

Start > Run > type Regedt32.exe and press Enter

  1. HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INIODBC Drivers and HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INI
  2. Right-click the key called ' (Default) ' and select Delete option.
  3. If unable to delete the key, double-click the key and erase the Data value entered. Once done, the value should read ' (value not set) '.
  4. Close the Registry Editor and re-launch the ODBC Data Source Administrator (ODBCAD32.exe).

On a x64 bit system for a x64 bit driver:

a. Go to Start Run and enter the following: odbcad32.exe (By default this will load the odbcad32.exe from C:WindowsSystem32odbcad32.exe).

Click OK and the Registry Editor will open.

On a x64 bit system for a x32 bit driver:

a. Go to the following path C:WindowsSysWOW64 and open the odbcad32.exe

(This will load the 32 bit version of ODBC Data Source Administrator)

Oracle Client Odbc Drivers 64 Bit

On a x32 bit system:

a. Go to Start Run and enter the following: odbcad32.exe (By default this will load the odbcad32.exe from C:WindowsSystem32odbcad32.exe).

Click OK and the Registry Editor will open.

We should be able to successfully see the drivers listed in the drivers Tab and should be able to create the DSN’s using that driver.

Or

1. To make this even easier we just need to execute the following command in elevated command prompt and refresh the registry

reg.exe DELETE 'HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INIODBC Drivers' /ve /f

and

reg.exe DELETE 'HKEY_LOCAL_MACHINESOFTWAREODBCODBCINST.INI' /ve /f

If you run into issues similar to this wherein the system DSN’s are missing please follow the below article.

Oracle Odbc Client 12

System DSN Entries Do Not Appear in ODBC Data Source Administrator (odbcad32.exe): http://support.microsoft.com/kb/2000277

Author : Krishnakumar Rukmangathan(MSFT), SQL Developer Engineer, Microsoft

Oracle 11g Client Odbc Driver 64 Bit

Reviewed by : Jason(MSFT), SQL Escalation Services, Microsoft