Oracle Data Provider for .NET, Managed Driver for ODAC 12.2c Release 1
Xcopy Installation Guide
Release 12.2.0.1.0 for ODAC 12.2c Release 1
May 2017
Copyright (c) Oracle Corporation 2017
This document provides information regarding the zip file contents and the
steps required to setup ODP.NET, Managed Driver xcopy installation.
New Features
The following features are newly supported in this release, but were not included in the documentation.
-
.NET Framework 4.7 certification
General Information
- The files in this zip file are NOT to be installed on top of an existing Oracle
Universal Installer (OUI) based Oracle Home installation.
- After unzipping the files, the product must be
installed and configured by executing install_odpm.bat.
- ODP.NET does not support usage of the "ALTER SESSION" statement to modify the Edition in Edition-Based Redefinition during the lifetime of a process.
- ODP.NET, Managed Driver and Distributed Transactions -
Using managed ODP.NET distributed transactions with Oracle.ManagedDataAccessDTC.dll is deprecated as it is primarily used with .NET Framework 4 releases
earlier than .NET 4.5.2. Microsoft has desupported these earlier .NET Framework 4 versions. Managed ODP.NET distributed transactions will continue to
be supported and enhanced with .NET Framework's native fully managed distributed transaction implementation.
Installation Instructions
- Download the ODP.NET, Managed Driver (xcopy version) zip file to a directory for staging.
- Unzip ODP.NET, Managed Driver (xcopy version) zip file to expand the contents to
your target install location.
The following
directories will be created:
a) odp.net - ODP.NET, Managed Driver files
b) network - sample .ORA files (i.e. tnsnames.ora and sqlnet.ora)
- If installing into an
existing xcopy home, uninstall the existing version by following the instructions
in the "Uninstallation Instructions" section of this README.
-
Execute install_odpm.bat to install and configure Oracle Data Provider for .NET, Managed Driver.
Note: Depending on the components to install/configure, administrative level privileges may be required.
Oracle recommends running the batch file under the "Run as Administrator" context.
install_odpm.bat takes the following arguments:
install_odpm.bat oracle_home_path platform [machine_wide_configuration]
Valid values for the required platform argument are: x86, x64, and both. No default value.
Valid values for the optional machine_wide_configuration argument are: true and false. Default=false.
If machine_wide_configuration option is true, ODP.NET assemblies are placed into the GAC
and machine.config is configured, which impacts the entire machine. However, if
machine_wide_configuration option is false, ODP.NET assemblies are not placed into the
GAC and machine.config is not modified. If setting machine_wide_configuration=false,
ungac pre-existing ODP.NET and Oracle ASP.NET provider assemblies from all homes
on the machine and unconfigure them from machine.config. This can be accomplished
by following the instructions in the "Uninstallation Instructions" section of this README.
For example, executing
install_odpm.bat c:\oracle x64 false
where machine_wide_configuration=false will install ODP.NET, Managed Driver to c:\oracle, but assemblies for ODP.NET, Managed Driver
will not be placed into the GAC and machine.config will not undergo any changes.
If machine wide configuration is not selected, customers may be required to configure the application's web/app.config
(for the configSections, DbProviderFactories, provider specific configuration sections, etc.). Customers will also need
to evaluate the usage of GAC for ODP.NET assemblies as ODP.NET installations into the GAC can force applications to load
those ODP.NET assemblies in the GAC over those located in the application's bin directory.