Oracle Universal Installer Version 11.2.0.0.0

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.

You will need to know where this directory is before proceeding.

  • For example, some syntactically valid connection strings follow:
    'user id=hr;password=hr;data source=//sales-server:1521/sales.us.acme.com'
    If the port number is not specified, 1521 is used by default.

  • TNSNAMES Setup

    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_HOMENetworkAdmin 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:
    ORACLE_HOMENetworkAdminSample
    to this directory:
    ORACLE_HOMENetworkAdmin

    <data source alias> =
    Oracle Universal Installer Version 11.2.0.0.0 Windows 10


    1. Consult the release notes first for any known issues or limitations.
    2. Check if the Oracle data access components were properly downloaded by comparing the download size to the one listed on the download page.
    3. If you have more than one Oracle Home installed on the same machine (e.g. Oracle 10g Release 2 client and Oracle 11g Release 2 client), by installing the Oracle 11.2 client, OUI will establish this client as the Oracle Home all your existing applications will use. For more information on using Multiple Oracle Homes, consult the ODP.NET documentation.
    4. It is highly recommended ODAC be installed into a new Oracle Home. Installing ODAC on top of an existing Oracle home may break existing Oracle applications. If you do install on top of an existing Oracle Home, make sure to stop all the Windows services using that Oracle Home (e.g. OracleMTSRecoveryService). Uninstall all the products in the existing Oracle Home before installing the new ODAC version.

    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.

    5. This installation provides policy configuration files that can redirect existing 10.2 and 11.1 ODP.NET applications to the current ODP.NET version. The policy files are located in the ORACLE_HOMEodp.netPublisherPolicy2.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.
    6. Installing ODP.NET into a new Oracle Home means that you will not have access to any of the Oracle Data Source aliases from your previous installation. To be able to use these existing data source attributes, copy the tnsnames.ora file in the ORACLE_HOMEnetworkadmin directory from your previous Oracle Home installation to the same directory in your new installation. Or you may create the connection aliases manually by following the Connection Setup Quick Start earlier.
    7. If errors indicating that 'MSVCR80.dll is not found' are observed, install the Visual C++ 2005 runtime libraries.



    Oracle Universal Installer Version 11.2.0.0.0 Windows 7

    Support and Bug Reports

    For any bugs and issues, you may participate in one of the OTN discussion forums for ODAC.

    Steps Oracle Universal Installer

    false ,