How To Install Both 32-bit and 64-bit ODP, OLEDB, And ODBC Oracle Software on 64-bit Windows

How To Install Both 32-bit and 64-bit ODP, OLEDB, And ODBC Oracle Software on 64-bit Windows [ID 795602.1]
		Modified 29-DEC-2011     Type BULLETIN     Status PUBLISHED

In this Document
  Purpose
  Scope and Application
  How To Install Both 32-bit and 64-bit ODP, OLEDB, And ODBC Oracle Software on 64-bit Windows
  References

---

Applies to:

Oracle Provider for OLE DB - Version: 10.2.0.1 to 11.2.0.2 - Release: 10.2 to 11.2
Oracle Data Provider for .NET - Version: 10.2.0.1.0 to 11.2.0.2   [Release: to 11.2]
Oracle ODBC Driver - Version: 10.2.0.1 to 11.2.0.2   [Release: 10.2 to 11.2]
Microsoft Windows (32-bit)
Microsoft Windows Itanium (64-bit)
Microsoft Windows x64 (64-bit)

Purpose

To help guide customers on how to install, configure, and test both the 32-bit and 64-bit Oracle Data Provider for .Net (ODP), Oracle Provider for OLE DB (OLEDB), and Oracle ODBC Driver (ODBC) Oracle Software on 64-bit Windows.

This bulletin will discuss the following:

1. Facts/Tips
2. How & What to Install for 32-bit and 64-bit Oracle Clients.
3. How to Test The 64-bit ODP, OLEDB, and ODBC
4. How to Test The 32-bit ODP, OLEDB, and ODBC

Scope and Application

This is intended for users trying to use ODP, OLE DB, and ODBC on 64-bit Windows.

How To Install Both 32-bit and 64-bit ODP, OLEDB, And ODBC Oracle Software on 64-bit Windows

When using the Oracle software on 64-bit Windows. Most will need to install both 32-bit and 64-bit Oracle software. First a few facts/Tips about 32-bit and 64-bit Oracle software installed on 64-bit Windows.

1. Facts/Tips:

• On 64-bit Windows, the 32-bit and 64-bit Oracle Software gets installed separately and used separately. The 64-bit Oracle software will not know the 32-bit Oracle software is installed. They are completely separate software when installing both 32-bit and 64-bit Oracle software on 64-bit Windows. IE. If your application runs in 32-bit then you need to install the 32-bit Oracle Software. 
• Do not install both 32-bit and 64-bit Oracle Software into the same directory or sub directory. They should not share any directory structure, otherwise when you try to remove the Oracle Home, it will remove both Oracle Homes. This is explained further in Document 1271661.1 De-install 11.2 32-bit Home Inadvertently Removes 64-bit Homes and Vice Versa.
• On 64-bit Windows the 64-bit software and 32-bit software are installed into two different places in the registry. For 64-bit Oracle software it will be located in:

  HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE

  For 32-bit Oracle software it will be located at:
  

  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ORACLE

• For ODP users: Oracle only installs into one assembly located under: c:\WINDOWS\assembly. If you look at the properties of the Oracle.DataAccess entry. If the Processor Architecture says x86 (or blank) then it is 32-bit. The only Oracle entries that have the Processor Architecture blank are for 1.x framework. If it says AMD64 or Itanium then it is 64-bit.
• To tell if an application is running in 32-bit or 64-bit mode. Run the application and look at the exe in Task Manager. If there is a * 32 behind the exe name, then the application is running in 32-bit.

2. How & What to Install for 32-bit and 64-bit Oracle Clients

Installation Note:

• When installing Oracle Software version 11.2 into both 32-bit and 64-bit Oracle homes on one 64-bit computer. The menu shortcuts for the Oracle Home are overwritten during the second Oracle installation. The solution to this problem is to set the Oracle homes names at a dos command line when running the Oracle Universal Installer (OUI). DO NOT RUN OUI from the menu shortcut. ie.

For installing setting manually the ORACLE_HOME_NAME add this option to the setup.exe command, for instance, for installing the 32-bit client:

setup.exe ORACLE_HOME_NAME=OracleClient32_home1

For installing the 64-bit client:

setup.exe ORACLE_HOME_NAME=OracleClient64_home1

This is due to Bug:10125991 "INSTALL ORACLE CLIENT 11.2 32-BIT AND 64-BIT ON SAME SYSTEM OVERRIDES SHORTCUT", which was filed due to the installation overwriting the menu shortcuts for the Oracle Homes. If the instructions to set the ORACLE_HOME at the command line when running the Universal Installer is used, this problem does not occur.

This is also explained in Document: 1243374.1 "Install Oracle Client 11.2 32-bit and 64-bit on Same System Overrides Entry on Programs Menu".

• When doing multiple installations on 64-bit Windows with the 11.2 Oracle software pre-requisite checks for disk, memory, and architecture fail if either the x86 client was installed first or the system was not rebooted. This has been filed as Bug 12408817 11.2 X64 CLIENT PREREQ'S FAIL IF X86 WAS INSTALLED FIRST, AND SYSTEM NOT REBOOTED. There are several workarounds to this :

• Change the order of the installs, install the x64 Oracle Software first.

• Ignore the x64 pre-requisite failures.

• Reboot between installs.

• After 32 bit install open Service Manager and stop the OracleRemExecServiceOracleRemExecService.
  This process is holding the resources needed to continue with the install.

TIP: When doing the install, name the installation directory with a name the indicates what is being installed. IE. Installing 32-bit Oracle client name the directory 32bitclient and for 64-bit Oracle client name the directory 64bitclient. That way when you look at the directory name you know exactly what was installed in it.

• 32-bit Oracle Client Installation:
  
  • Install the Oracle Client and ODP, OLE DB, and ODBC for 32-bit Windows. For this example we will call the oracle home 32bitclient and assume it was installed on the c:\ drive.
  • If installing the 10.2 Oracle Software please install in the following order:
    1. 10.2.0.1.0 Oracle Client & ODBC Driver
    2. 10.2.0.2.20 ODAC (available here) - This will install ODP and OLE DB.
    3. 10.2.0.4.0 Oracle Database Patch 6810189 or higher. Due to an installation bug with odbc, do not install the 10.2.0.3.0 Oracle Database patch. See Note 403021.1 "An Unsupported Operation was Attempted" Error When Trying to Create DSN With ODBC 10.2.0.3.0 for more information.
  • The only installation order for 11.1 is to install the 11.1 Oracle Client,ODBC, ODP, and OLEDB first. Then apply any Oracle Database patchsets, if needed to fix a specific issue.
• 64-bit Oracle Client Installation:
  • For 64-bit Oracle clients, install the Oracle client and ODBC from the Oracle client installation into the 64bitclient Oracle home. Then install the ODAC (available here) to install ODP and OLEDB into the 64bitclient Oracle home.
  • Then apply the 64-bit 10.2.0.4.0 Oracle Database Patch 6810189 to get the latest client, odbc, ODP, and OLEDB.
• Configuring the Sqlnet Clients:
  • Run the Net Configuration Assistant located under Start -> All Programs -> Oracle -> Oracle_Home_Name -> Configuration and Migration Tools -> Net Configuration Assistant for both the 64-bit Oracle software and 32-bit Oracle software. Since both will need to have the sqlnet connection configured. The configuration for this is exactly the same for both 32-bit and 64-bit. Here are the instructions:
    
    1. In the Oracle Net Configuration Assistant: Welcome screen select Local Net Service Name Configuration and click on the Next > button.
    2. In the Oracle Net Configuration Assistant: Net Service Name Configuration screen, select add and click on the Next > button.
    3. In the Oracle Net Configuration Assistant: Net Service Name Configuration, Service Name screen, add the Service Name (AKA SID) and click on the Next > button.
    4. In the Oracle Net Configuration Assistant: Net Service Name Configuration, Select Protocols screen, select your protocol (typically TCP) and click on the Next > button.
    5. In the Oracle Net Configuration Assistant: Net Service Name Configuration, TCP/IP Protocol screen, add the Host Name (typically the name of the server or IP address), if your server is not using the default port of 1521, then select the "Use another port number" and add the port. Then click on the Next > button.
    6. In the Oracle Net Configuration Assistant: Net Service Name Configuration, Test screen, select Yes, perform a test. Click on the Next > button. It will now try to connect to the server using the information provided. It should come back with "Connecting...Test successful.". Click on the Next> button.
    7. In the Oracle Net Configuration Assistant: Net Service Name Configuration, Net Service Name screen, add the Net Service Name (AKA sqlnet alias) you want to use to connect to your Oracle Database. Click on the Next > button. Let it default to No to add another service name. Click on the Next> button. Click on the Next> button again. Then click on the Finish button. This now completes setting up the sqlnet configuration.

3. How to Test The 64-bit ODP, OLEDB, and ODBC

• Testing the Oracle Data Provider for .Net 64-bit Configuration:
  • Since there is no "test connection" button or device used to test out ODP. The easiest way to test ODP is to use the instructions and code in Note 760958.1 HOWTO: Test ODP.NET Install Using Command Line Compilation.
• Testing the Oracle Provider for OLE DB 64-bit Configuration:
  
  • Note 280028.1 HOWTO Test an OLEDB connection with a UDL file
• Testing the Oracle ODBC Driver 64-bit Configuration
  1. Select Start -> Run, type the following after Open: C:\Windows\system32\odbcad32.exe.
  2. Select either User DSN or System DSN. User DSN is the dsn that will be saved only for that user. System can be used by any user logged into the machine. Click on Add...
  3. Select the Oracle ODBC Driver from the list. Then click on Finish.
  4. Add the name you want for the Data Source Name, select your Net Service Name where is says TNS Service Name. You can either use the arrow to select from a list that is populated by reading the tnsnames.ora file or enter the value manually.
  5. Click on the Test Connection button (on the right side of the screen). It will come up with the "Oracle ODBC Driver Connect" screen. Type in your Service Name (aka TNS Service Name), User Name, and Password. Then click on OK. If the connection is successful, it will come back with the pop up box saying "Connection successful".  

4. How to Test The 32-bit ODP, OLEDB, and ODBC

• Testing the Oracle Data Provider for .Net 32-bit Configuration:
  • Since there is no "test connection" button or device used to test out ODP. The easiest way to test ODP is to use the Getting Started  With Oracle Data Provider for .Net Code for either C# or Visual Basic on otn.
• Testing the Oracle Provider for OLE DB 32-bit Configuration:
  • Note 405743.1 Test a 32-bit OLEDB connection with a UDL file on 64-bit Windows
• Testing the Oracle ODBC Driver 32-bit Configuration: The biggest problem with testing the 32-bit Oracle ODBC Driver on 64-bit Windows. Is running the correct odbc administrator. Here are the instructions to start the right odbc administrator and test the odbc driver:

1. Select Start -> Run, type the following after Open: C:\Windows\SysWOW64\odbcad32.exe to run the 32-bit ODBC Administrator. See Note 308645.1 32-Bit ODBC Driver Not Listed in 64-Bit Microsoft ODBC for further details on the 32-bit ODBC administrator on 64-bit Windows.
2. Select either User DSN or System DSN. User DSN is the dsn that will be saved only for that user. System can be used by any user logged into the machine. Click on Add...
3. Select the Oracle ODBC Driver from the list. Then click on Finish.
4. Add the name you want for the Data Source Name, select your Net Service Name where is says TNS Service Name. You can either use the arrow to select from a list that is populated by reading the tnsnames.ora file or enter the value manually.
5. Click on the Test Connection button (on the right side of the screen). It will come up with the "Oracle ODBC Driver Connect" screen. Type in your Service Name (aka TNS Service Name), User Name, and Password. Then click on OK. If the connection is successful, it will come back with the pop up box saying "Connection successful".