================================================
Oracle Data Access Components (ODAC) 11.1.0.6.20
================================================
Copyright (c) 2007, Oracle. All rights reserved.
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.
=================
Table of Contents
=================
I. Notes & Information
II. Installation Instructions
======================
I. Notes & Information
======================
1) The files of this zip file is NOT to be installed on top of an existing
Oracle Universal Installer (OUI) based Oracle Home installation.
2) After unzipping the files, products must be installed and
configured by executing the install.bat.
==============================
II. Installation Instructions
==============================
1. Download the ODAC (xcopy version) zip file to a directory for staging
ODAC products.
2. Unzip ODAC (xcopy version) zip file to expand the contents.
The following directories will be created:
a) instantclient_11_1 - Oracle Instant Client
b) ODP.NET1x - Oracle Data Provider for .NET 1.x
c) ODP.NET20 - Oracle Data Provider for .NET 2.0
d) ASP.NET - Oracle Providers for ASP.NET
e) OLEDB - Oracle Provider for OLEDB
f) OO4O - Oracle Objects for OLE
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.
3. 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.x:
install.bat odp.net20 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\Sofware\Oracle\KEY_odac. Note that ODP.NET registry entries are
simply created under HKLM\Software\Oracle\ODP.NET\, and not under
HKLM\Sofware\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 WIHTOUT 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 1.x depends on
- Oracle Instant Client
b) Oracle Data Provider for .NET 2.0 depends on
- Oracle Instant Client
c) Oracle Providers for ASP.NET depends on
- Oracle Instant Client
- Oracle Provider for ADO.NET 2.0
d) Oracle Provider for OLEDB depends on
- Oracle Instant Client
e) Oracle Objects for OLE 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.net c:\oracle odac false
will only install and configure ASP.NET and not install and configure
ODP.NET 2.0 or instant client. If the last argument is not specified,
the product and its dependencies will be installed and configured.
4. 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.
5. Note that install.bat sets the value of the NLS_LANG registry key at
HKLM\Sofware\Oracle\KEY_ to AMERICAN_AMERICA.WE8MSWIN1252
by default. Please modify install.bat or change this value in the registry
after the install if necessary.
6. 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.
7. 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.
=================================
III. UnInstallation Instructions
=================================
1. 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
Each product can be also be unconfigured and uninstalled individually.
As an example, executing the following will uninstall only ODP.NET 2.x:
uninstall.bat odp.net20 odac
where "odac" is the Oracle Home Name that was used at install time.
The uninstall.bat does not uninstall the product's depenencies. This means
that the above example will only uninstall ODP.NET 2.x only and not it's
dependencies.
2. Remove the install directory and install directory's bin subdirectory
from the system PATH environment variable.
|