Oracle.ManagedDataAccess 23.3.3-dev
Oracle.ManagedDataAccess 23.3.3-dev
Release Notes for Oracle Data Provider for .NET, Managed Driver NuGet Package
April 2024
Managed Oracle Data Provider for .NET (ODP.NET) features optimized ADO.NET data access to the Oracle database for .NET Framework and is 100% managed code. ODP.NET allows developers to take advantage of advanced Oracle database functionality, including AI vectors, Real Application Clusters, Application Continuity, JSON Relational Duality, and Fast Connection Failover.
This document provides information that supplements the Oracle Data Provider for .NET (ODP.NET) documentation.
Oracle .NET Links
- Oracle .NET Home Page
- GitHub - Sample Code
- ODP.NET Discussion Forum
- YouTube
- X (Twitter)
- Email Newsletter Sign Up
New Features
- Transparent Application Failover (TAF)
- ODP.NET TAF is a client-side high availability feature that enables a client apps to automatically reconnect to a secondary database instance if the connected primary instance fails or shuts down. ODP.NET Core and managed ODP.NET now support TAF session failover and call backs. For more information, review the ODP.NET TAF documentation PDF included with this NuGet package.
- Performance Improvements
- ODP.NET 23c authentication is now faster for the first new connection.
Bug Fixes since Oracle.ManagedDataAccess.Core 23.3.2-dev
- Bug # - title
Installation Changes
The following app/web.config entries are added when installing the managed ODP.NET NuGet package to your application:
- Configuration Section Handler
A configuration section handler entry is added to the app/web.config to enable applications to add an <oracle.manageddataaccess.client> section for ODP.NET, Managed Driver-specific configuration.
Note: For a web app, if the same config section handler for "oracle.manageddataaccess.client" also exists in machine.config but the "Version" attribute values are different, an error message "There is a duplicate 'oracle.manageddataaccess.client' section defined." may be observed at runtime. To resolve the error, remove the "oracle.manageddataaccess.client" config section handler entry in the machine.config. If other applications on the machine depend on this machine.config entry, move the config section handler entry to each application's web.config file.
- DbProviderFactories
The DbProviderFactories entry is added for applications that use DbProviderFactories and DbProviderFactory classes. Any DbProviderFactories entry for "Oracle.ManagedDataAccess.Client" in the machine.config will be ignored.
- Dependent Assembly
The dependent assembly entry is created to ignore policy DLLs for Oracle.ManagedDataAccess.dll. It directs the app to always use the Oracle.ManagedDataAccess.dll version that is specified by the "newVersion" attribute in the "bindingRedirect" element. The "newVersion" attribute corresponds to the Oracle.ManagedDataAccess.dll version which came with the NuGet package.
- Data Sources
The data sources entry is added to provide a template on how a data source can be configured in the app/web.config. Simply rename the sample data source to an alias of your choosing; modify the PROTOCOL, HOST, PORT, SERVICE_NAME as required; and un-comment the "dataSource" element. Once that is done, the alias can be used as the "data source" attribute in your ODP.NET connection string.
Copyright (c) 2024, Oracle and/or its affiliates.