ODP.NET Oracle.ManagedDataAccess causes ORA-12537 network session end of file

Question

Overview

I want to replace Oracle.DataAccess with Orcale.ManagedDataAccess, but opening a connection with the latter throws an ORA-12537 netwo

Answer 1

Edit: ASO is now supported. Upgrade to ODAC 12c Release 4 or later. If this does not fix your problem, check the alert.log on the database server and investigate (google) any errors that occur there when you attempt to connect.

---

Original Answer:

As of this writing (4/30/15) there is no support for Oracle Advanced Security Option (ASO) encryption with ODP.NET Managed Driver which is what is causing your errors.

This is very likely to be supported at some point in the future so if you are reading this at a later date, check the latest ODP.NET docs to see if an upgrade of ODP.NET is needed.

http://docs.oracle.com/cd/E56485_01/win.121/e55744/InstallConfig.htm#CHDJIDIG

Answer 2

Had some of the same problems. Found an entry in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\wow6432\oracle. If this part contains a ODP.NET.managed entry, possible with another key (name version dependend) check if this entyr contains a string called TNS_ADMIN. This string should be deleted or the value changed to a not existing directory. If the string exists and point to a valid directory the Managed Client does not use the setting from the configuration file and fails. Further investigation should be used, but I got my stuff working, and must postpone the rest....

Answer 3

I too struggled with this error. Finally i tried with Oracle.ManagedDataAccess.dll for 12c (Version 4.122.1.0). Created a reference for above dll from the ODAC installed directory (\odp.net\managed\common), it worked...!!! Sharing my solution.

Answer 4

As of October 5th, 2015, the Oracle.ManagedDataAccess driver (ODAC 12c Release 4) supports ASO.

https://apex.oracle.com/pls/apex/f?p=18357:39:18138408495219::NO::P39_ID:28201

Answer 5

I had was getting this error, and it was a simple case that my query that I was running had a mistake.

Answer 6

Make sure that you do not have older versions of Oracle.ManagedDataAccess in the GAC. It seems that several versions of the dll have the same AssemblyVersion.

I had an older version in the CLR 4 GAC (C:\Windows\Microsoft.NET\assembly\GAC_MSIL for me) that got installed with a Oracle 12.1-client.

Since dll:s in the GAC always are used first the old ASO-uncapable version was used, but I thought that I used the newer version.

Solution was to uninstall the older version from the GAC. The first installation step in the 12.1.2400 Nuget Package Readme-file is to "Un-GAC and unconfigure any existing assembly".