Download includes the following products:
a) Oracle Developer Tools for Visual Studio (184.108.40.206.0)
b) Oracle Data Provider for .NET 4 (220.127.116.11.0)
c) Oracle Data Provider for .NET 2 (18.104.22.168.0)
d) Oracle Providers for ASP.NET 4 (22.214.171.124.0)
e) Oracle Providers for ASP.NET 2 (126.96.36.199.0)
f) Oracle Database Extensions for .NET 4 (188.8.131.52.0)
g) Oracle Database Extensions for .NET 2 (184.108.40.206.0)
h) Oracle Services for MTS (220.127.116.11.0)
i) Oracle Provider for OLE DB (18.104.22.168.0)
j) Oracle Objects for OLE (22.214.171.124.0)
k) Oracle ODBC Driver (126.96.36.199.0)
l) Oracle SQL*Plus (188.8.131.52.0)
m) Oracle Instant Client (184.108.40.206.0)
n) Oracle Universal Installer (220.127.116.11.0)
The following items are required for ODAC:
Additional Notes on Requirements:
Note: Visual Studio Express Editions are not supported with the Oracle Developer Tools. However, ODP.NET is supported with Visual Studio Express Edition.
Note: Microsoft introduced changes to the Distributed Transaction Coordinator (DTC) with Windows Vista and Windows Server 2008. Oracle Services for MTS support this new DTC when the minimum operating system level is Windows Vista with Service Pack 1 or Windows Server 2008.
The instructions below apply to installing ODAC using Oracle Universal Installer. Xcopy installation instructions are included with the download itself.
Note: If an ODAC beta is installed, uninstall it before installing this ODAC release.
There are a number of methods to connect Oracle client to a database server. Two of the most common include EZCONNECT and TNSNAMES. EZCONNECT is the easiest to setup. TNSNAMES is much more maintainable in the long term. If you are new to Oracle, we recommend you use EZCONNECT. You only have to choose one or the other to connect.
These quick start instructions assume you have a valid username and password for the database server.
Note: In the setup instructions below, ORACLE_HOME represents the directory where the Oracle client Home was installed on your machine. A typical directory for an OUI Oracle client Home is:
You will need to know where this directory is before proceeding.
to this directory:
This file tells the Oracle client by what methods (e.g. EZCONNECT) Oracle client can connect to the Oracle database server.
For example, some syntactically valid connection strings follow:
"user id=hr;password=hr;data source=//sales-server:1521/sales.us.acme.com" "user id=hr;password=hr;data source=//sales-server/sales.us.acme.com" "user id=hr;password=hr;data source=sales-server/sales.us.acme.com"
If the port number is not specified, 1521 is used by default.
An Oracle Net service name allows the Oracle client to use a simple alias to connect to the database server. The alias definition contains all the information needed to create a connection to the database server. Alias information is stored in the tnsnames.ora file typically located in the ORACLE_HOME\Network\Admin directory. This alias is used as the data source value in your connection string. ODAC installations do not create a tnsnames.ora file so you need to create one. Alternatively, you can copy an existing tnsnames.ora file from an existing Oracle client installation to your new ODAC installation. The following instructions assume you will have to create a new tnsnames.ora file.
1. Copy the tnsnames.ora file located in the following directory:
to this directory:
ORACLE_HOME\Network\Admin\ <data source alias> = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = <hostname or IP>)(PORT = <port>)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = <database service name>) ) )
The data source alias, hostname/IP, port, and database service name in the tnsnames.ora should be modified appropriately. If the TNS entries in the ORACLE_HOME\network\admin\tnsnames.ora file are not recognized by the Oracle client, create a ORACLE_HOME\oracle.key file using any text editor and type in the following line:
<home key> is the registry key for the ODAC Oracle Home. For example, if the default Oracle Home location was used during the install, the proper entry for the oracle.key file would be the following:
Check whether oci.dll in the existing ORACLE_HOME directory has been removed during the uninstall process. If oci.dll was not removed, follow these steps to remove the DLL.
a) Rename oci.dll to oci.dll.delete.
b) Reboot your machine.
c) Delete oci.dll.delete, which should no longer be in use after rebooting.
d) Install the new ODAC.
ORACLE_HOME\odp.net\PublisherPolicy\2.x directory. In addition, the installation of ODP.NET will place ODP.NET policy DLLs into the GAC so that existing applications can start using the newly installed ODP.NET version immediately. However, if this is not desired, be sure to remove the policy DLLs from the GAC.
The PDF and HTML documentation can be viewed from the ORACLE_HOME\ODACDoc\DocumentationLibrary\welcome.html page. To view this page, go to Start Menu --> Oracle - <Oracle Home> --> Application Development --> Oracle Data Access Components Documentation.
Additionally, the Oracle documentation is installed as part of Visual Studio Dynamic Help.
For any bugs and issues, you may participate in one of the OTN discussion forums for ODAC.