=========================================
Oracle Data Provider for .NET 10.2.0.3.03
=========================================
Copyright (c) 2007, Oracle. All rights reserved.

This document provides information that supplements the Oracle Data 
Provider for .NET (ODP.NET) documentation.

=================================
Bugs Fixed in ODP.NET 10.2.0.3.03
=================================
5916667 - ODP.NET PATCH INTRODUCES ORA-24338 IN CODE THAT WORKED IN PREVIOUS 
          VERSIONS

This patch requires an installation of ODP.NET 10.2.0.2.0 or later
prior to applying this patch.

NOTE: For best performance, download and apply Oracle Client 10.2.0.2.0 Patch 
1 or later.

The rest of the readme.txt is divided into two sections.
I.  IMPORTANT INSTALLATION INFORMATION for 2.102.3.3
II. OPTIONAL CONFIGURATION INFORMATION FOR ODP.NET 10.2.0.3.02 AND HIGHER

=====================================================
I. IMPORTANT INSTALLATION INFORMATION for 2.102.3.3
=====================================================
ODP.NET 2.102.3.3 is ODP.NET 10.2.0.3.03 built with the .NET 2.x framework.
It is a PSE (Patchset Exception) that can be applied on top of 2.102.3.0 
version of ODP.NET

Below are the steps for applying this PSE.

1) Shutdown any application using Oracle Data Provider for .NET.

2) Expand the zip file.

3) Copy the following file from the \2.102.3.3 directory to the 
   <Oracle Home>\ODP.NET\bin\2.x directory

     a) Oracle.DataAccess.dll

4) Copy the following files from the \2.102.3.3 directory to your 
   <Oracle Home>\bin.

     a) OraOps10w.dll

5) Create a new directory <Oracle Home>\ODP.NET\PublisherPolicy\2.x and
   copy the new publisher policy files listed below from the \2.102.3.3 
   directory to the newly created directory

     a) Policy.2.102.Oracle.DataAccess.dll
     b) Policy.2.102.Oracle.DataAccess.config 

6) Open a Visual Studio .NET 2005 command prompt

7) Navigate to the <Oracle Home>\ODP.NET\bin\2.x directory

8) Execute the following to uninstall your existing version of the 
   ODP.NET assembly:

     gacutil /u Oracle.DataAccess

   NOTE: If you do not have gacutil.exe, you can navigate to 
   %SystemRoot%\assembly using Windows File Explorer, right-click on 
   each .NET 2.x version of Oracle.DataAccess, and click Uninstall.  
   The same applies to policy DLLs.

9) Execute the following to install the new ODP.NET assembly:

     gacutil /i Oracle.DataAccess.dll

   NOTE: If you do not have gacutil.exe, you can drag-and-drop the 
   Oracle.DataAccess.dll to %SystemRoot%\assembly using Windows File Explorer.
   The same applies to policy DLLs.

10) Rename the the registry key for the previously installed version of 
    ODP.NET from HKLM\Software\Oracle\ODP.NET\<previous version> to 
    HKLM\Software\Oracle\ODP.NET\2.102.3.3

    NOTE: <previous version> refers to the version of ODP.NET for which 
    this patch is applied.

11) Navigate to the <Oracle Home>\ODP.NET\PublisherPolicy\2.x directory

12) Execute the following to redirect all application references of 
    2.102.x ODP.NET to 2.102.3.3 (this Patchset):

      gacutil /i Policy.2.102.Oracle.DataAccess.dll

==========================================================================
III. OPTIONAL CONFIGURATION INFORMATION FOR ODP.NET 10.2.0.3.02 AND HIGHER
==========================================================================

1) This version of ODP.NET contains the following two new features:
   a) FetchSize registry support

      This feature enables applications to configure the default amount of data
      ODP.NET fetches from the database for every server round trip.  If the
      FetchSize registry does not exist, the default size ODP.NET uses is 65536 
      bytes.  The larger the FetchSize, less server round trip the application 
      will need to incur, but more memory the application will require.  The 
      smaller the FetchSize, more server round trip the application will need 
      to incur, but less memory the application will require.  This registry 
      value is meant to fine-tune our application to optimize speed and memory 
      usage based on application's needs.

   b) PromotableTransaction registry and "Promotable Transaction" connection 
      string attribute support 

      This feature enables applications to use local transactions with 
      System.Transactions where previous versions of ODP.NET supported only
      distributed transactions with System.Transactions.  If the
      PromotableTransaction registry does not exist, the default value of 
      "promotable" is used.  If "promotable" is specified, first and subsequent
      connections opened in the same TransactionScope will enlist in the same
      distributed transaction.  If "local" is specified, the first connection
      opened in the TransactionScope will use a local transaction.  If any 
      subsequent connections are opened within the same TransactionScope, 
      an exception will be thrown.  If there are connections opened already
      in the TransactionScope and an OracleConnection with
      "Promotable Transaction=local" is attempted to be opened within the same
      TransactionScope, an exception will also be thrown.  

      The registry entry for a particular version of ODP.NET will apply for
      all applications using that version of ODP.NET.  To override the 
      value specified in the registry, the "Promotable Transaction" connection
      string attribute should be set to either "promotable" or "local".

      This feature requires .NET Framework 2.0 or higher.

2) Configuring FetchSize in the Registry

   Within HKLM\Software\Oracle\ODP.NET\2.102.3.3, add a new string value 
   (REG_SZ) called "FetchSize" (one word).  Assign this new registry entry with 
   the default fetch size.  If this registry entry does not exist, the default 
   of 65536 bytes is used.

   The same can be applied for HKLM\Software\Oracle\ODP.NET\1.102.3.3.

3) Configurating PromotableTransaction in the Registry

   Within HKLM\Software\Oracle\ODP.NET\2.102.3.3, add a new string value 
   (REG_SZ) called "PromotableTransaction" (one word).   Assign this new 
   registry entry with the default type of transaction that ODP.NET should 
   create within the context of system.transactions.  If this registry entry 
   does not exist, the default value is "promotable".  Two valid values for 
   this registry entries are: "promotable" and "local".
