Oracle Data Provider for .NET is part of Oracle Data Access Components (ODAC), which can be downloaded from OTN. Beginning with ODAC 18.104.22.168.20, Oracle Data Provider for .NET can be installed through XCopy or Oracle Universal Installer.
Administrators use XCopy to deploy Oracle Data Provider for .NET to large numbers of computers for production deployments. The XCopy has a smaller installation size and fine-grain control during installation and configuration than Oracle Universal Installer.
Oracle Universal Installer (OUI)
Developers and administrators use Oracle Universal Installer for automated ODP.NET installations. It includes documentation and code samples that are not part of the XCopy.
Note:This section describes installation using the Oracle Universal Installer. For installation and configuration using the XCopy install, refer to the README.TXT file that is part of the XCopy installation.
Additionally, Oracle Data Provider for .NET Dynamic Help is registered with Visual Studio, providing context-sensitive online help that is seamlessly integrated with Visual Studio Dynamic Help. With Dynamic Help, the user can access ODP.NET documentation within the Visual Studio IDE by placing the cursor on an ODP.NET keyword and pressing the F1 function key.
Oracle Data Provider for .NET creates an entry in the
machine.config file of the computer on which it is installed, for applications using the
OracleClientFactory class. This enables the
DbProviderFactories class to recognize ODP.NET.
ODP.NET, Unmanaged Driver Entity Framework 6 and Code First functionality are available through a NuGet package. OUI and Xcopy installations include this package as well, but require post-install configuration steps. The NuGet package for ODP.NET, Unmanaged Driver Entity Framework automates these post-install steps, except for the application-specific connection string settings.
Oracle.DataAccess.dll assembly is installed to the following locations:
.NET Framework 2.0:
.NET Framework 4:
Note:If the machine has the corresponding .NET Framework installed, then the
Oracle.DataAccess.dllassembly is added to the Global Assembly Cache (GAC) as well. This is to ensure 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.
Documentation and the
readme.txt file can be accessed through
Samples are provided in the
ODP.NET consists of managed and unmanaged binaries. Through the use of the
DllPath configuration parameter, each application can specify the
\bin location that the dependent unmanaged Oracle Client binaries are loaded from. However, the
ORACLE_BASE\\ORACLE_HOME must have the same ODP.NET version installed as the version that the application uses. Otherwise, a version mismatch exception is thrown.
Oracle.DataAccess.dll searches for dependent unmanaged DLLs (such as Oracle Client) based on the following order:
Directory of the application or executable.
DllPath setting specified by application config or
DllPath setting specified by
DllPath setting specified by the Windows Registry.
Directories specified by the Windows
PATH environment variable.
Upon installation of ODP.NET, Oracle Universal Installer sets the
DllPath Windows Registry value to the
\bin directory where the corresponding dependent DLLs are installed. Developers must provide this configuration information on an application-by-application basis.
When a new ODP.NET version is installed, default values are set in the Windows Registry for the new version. Because the policy DLLs redirect all ODP.NET references to this new ODP.NET version, applications use the default values. Developers can provide a config or
web.config file specific to the application to prevent this redirection. The configuration file settings always apply to the application, regardless of whether or not patches or new versions are installed later.
ODP.NET Configuration File Support is only available for version 10.2.0.4 and later.
Oracle.DataAccess.dllfor .NET Framework 2.0 and
Oracle.DataAccess.dllfor .NET Framework 4 use the same unmanaged DLL,