Oracle Data Access Components (ODAC) 11.2.0.4.0
Installation Guide
and Release Notes
Release 11.2.0.4.0 Production
January 2014
Copyright (c) Oracle Corporation 2014
This document provides information regarding the contents on the zip file and the
steps required to setup Oracle Data Access Components into an Oracle Instant
Client Home.
Notes & Information
- The files of this zip file is NOT to be installed on top of an existing Oracle
Universal Installer (OUI) based Oracle Home installation.
- After unzipping the files, products must be installed and
configured by executing the install.bat.
Installation Instructions
- Download the ODAC (xcopy version) zip file to a directory for staging ODAC
products.
- Unzip ODAC (xcopy version) zip file to expand the contents.
The following
directories will be created:
a) instantclient_11_2 - Oracle Instant Client
b)
ODP.NET20 - Oracle Data Provider for .NET 2
c) ODP.NET4 - Oracle Data Provider
for .NET 4
d) ASP.NET - Oracle Providers for ASP.NET 2
e) ASP.NET4 - Oracle
Providers for ASP.NET 4
f) OLEDB - Oracle Provider for OLEDB
g) OraMTS - Oracle Services for MTS
The install.bat will also be
extracted to the same location as the ODAC zip file, which is used to install
and configure a specific product.
- Execute install.bat to install and configure ODAC products.
To install all ODAC
products, execute the following:
install.bat all c:\oracle odac
Each product can
be also be installed and configured individually. As an example, executing the
following will install only ODP.NET 2:
install.bat odp.net2 c:\oracle odac
where "c:\oracle", for example, is your installation directory and "odac" is the
Oracle Home Name that is used for the registry keys. In this example, the
registry entries for this install is created under HKLM\Software\Oracle\KEY_odac.
Note that ODP.NET registry entries are simply created under
HKLM\Software\Oracle\ODP.NET\, and not under HKLM\Software\Oracle\KEY_.
If multiple products are installed to the same destination directory, make sure
that the Oracle Home Name that is specified as an argument to install.bat is the
same for all those products.
By default, when install.bat is executed for a
given product, the product and its dependencies will be installed and configured
WITHOUT a check to see if there is a newer version of the product or its
dependencies already installed.
Below is the product dependency information:
a)
Oracle Data Provider for .NET 2 depends on
- Oracle Instant Client
b) Oracle
Data Provider for .NET 4 depends on
- Oracle Instant Client
c) Oracle Providers
for ASP.NET 2 depends on
- Oracle Instant Client
- Oracle Data Provider for .NET
2
d) Oracle Providers for ASP.NET 4 depends on
- Oracle Instant Client
- Oracle
Data Provider for .NET 4
e) Oracle Provider for OLEDB depends on
- Oracle
Instant Client
f)
Oracle Services for MTS depends on
- Oracle Instant Client
To not have the
products dependencies installed and configured, execute install.bat with 'false'
as the fourth parameter.
For example, executing
install.bat asp.net2 c:\oracle
odac false
will only install and configure ASP.NET 2 and not install and
configure ODP.NET 2 or instant client. If the last argument is not specified,
the product and its dependencies will be installed and configured.
- Add the install directory and install directory's bin subdirectory to the system
PATH environment variable before any other Oracle directories. Otherwise, the
products that are installed may not work properly as it will not be able to load
the necessary DLLs. for example, if c:\oracle was provided as the install
directory, add c:\oracle and c:\oracle\bin to the system PATH.
- Note that install.bat sets the value of the NLS_LANG registry key at
HKLM\Software\Oracle\KEY_ to AMERICAN_AMERICA.WE8MSWIN1252 by
default. Please modify install.bat or change this value in the registry after
the install if necessary.
- If OraMTS is installed, the OracleMTSRecoveryService is created with the
LocalSystem account as the logon account. The credentials can be changed using
the "services" administration tool. Please read the OraMTS readme.txt for
details. Note that after the install or the configuration, the service will not
be started, since it requires the install directory and its bin directory to be
included in the system PATH.
- Application using components from ODAC can use EZ CONNECT to connect to Oracle
without depending on tnsnames.ora. Otherwise, configure or copy over
tnsnames.ora from another machine and set TNS_ADMIN or ORACLE_HOME environment
variable appropriately.
UnInstallation Instructions
- Execute uninstall.bat from the Oracle Home installation directory to unconfigure
and uninstall ODAC products.
To uninstall all ODAC products, execute the
following:
uninstall.bat all odac
or
uninstall.bat all c:\oracle
Each product can be also be unconfigured and
uninstalled individually. As an example, executing the following will uninstall
only ODP.NET 4:
uninstall.bat odp.net4 odac
or
uninstall.bat odp.net4 c:\oracle
where "odac" is the Oracle Home
Name that was used at install time and "c:\oracle" is the installation directory. The uninstall.bat does not uninstall the
product's dependencies. This means that the above example will only uninstall
ODP.NET 4 and not it's dependencies.
- Remove the install directory and install directory's bin subdirectory from the
system PATH environment variable.
Notes
- For backward compatibility, install.bat will still accept arguments odp.net20
and asp.net to install Oracle Data Provider for .NET 2 and Oracle Providers for
ASP.NET 2.
- The install and uninstall scripts log all operations to the destination
directory's install.log and uninstall.log.