Excerpt from: http://www.cnblogs.com/shelvenn/p/3799849.html
I am using Windows 10, 64-bit operating system.
1. Download the driver package
Base pack: Instantclient-basic-windows.x64-11.2.0.3.0.zip
ODBC Package: Instantclient-odbc-windows.x64-11.2.0.3.0.zip
I downloaded 11.2.0.3 version, two package version must be consistent. Http://www.oracle.com/technetwork/topics/winx64soft-089540.html
2. Unzip the installation
Unzip the above two packages, put the extracted files in the same directory (merge), note that 2 packets after the decompression of all the files must be placed in a directory, assuming that the d:\\instantclient_11_2
Open cmd with administrator privileges, enter the directory, run Odbc_install.exe to install.
After the installation is successful, run the 64-bit ODBC driver configuration program "C:\windows\SysWOW64\odbcad32.exe"
Note: The Odbcad32.exe directory for the 64-bit system should be in SysWOW64.
No accident, the ODBC driver has been installed successfully, open ODBC data Source Administrator can see the ODBC driver entry:
3. Select the ODBC configuration DSN, for example, can be based on the actual situation of the world Oracle ODBC Driver configuration.
Click Test Connection to enter a password for connection testing verification
After the test connection is successful, you can use ODBC to connect to the database, Enjoy it!
In addition, I use ADO to block ODBC connections. The ODBC connection string test is successful and can be used: PROVIDER=MSDASQL.1; Persist Security Info=false; User ID=AVLS; Password=1;data SOURCE=ORCL;
and send an Oracle ODBC connection string Rollup: http://www.connectionstrings.com/oracle/So many people contribute really good!
Again: Configuring an Oracle ODBC driver requires the configuration environment variable, which allows the driver to find the Tnsnames.ora below D:\instantclient_11_2\NETWORK\ADMIN The Tnsnames.ora file contains a connection string to the Oracle server;
You only need to configure the value of the ORACLE_HOME environment variable to D:\instantclient_11_2. It has been tested, hehe. Thank you, no compliments, very useful.
With regard to environment variables, there is also an ODBC-driven language setting that needs to be configured, Nls_lang:simplified Chinese_china. ZHS16GBK current test can solve the problem of SQL query Chinese garbled by ODBC.
Reference connection: http://bbs.51cto.com/thread-1037322-1.html
Oracle Configuration ODBC