For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!
As an update, this seems to happen if sqlnet.ora is found at all. I can remove everything from sqlnet.ora it and it still happens. If I rename sqlnet.ora to something else, the problem goes away, it picks up tnsnames.ora, and things work just fine.
Just posting to add that it's still an issue with the 3.1 release version.
My dev team found the bug. It looks like a regression. We filed a bug (31867606) on your behalf and will work on a fix.
Great, thank you!
We are experiencing the same issue.
As a workaround I have renamed the sqlnet.ora. I am not sure if this causes any side effects.
We have already filed an issue on github: https://github.com/oracle/dotnet-db-samples/issues/99
This bug has been fixed and will be part of our next ODP.NET 19.10 release.
While you're waiting for a fix, there are a couple workarounds. You can either:
Including the package System.DirectoryServices.Protocols solved the problem for us.
Many thanks for the quick response.
It seems like the the core version is prone to this, too. Are you aware of that ?
Ok this was non-sense... I´m sorry... The question to ask would be: What exactly do I need to get the fix ? Using Oracle.Enitity.Framework.Core 3.19.80 still results in that issue - I still need to include the protocols package...
Oracle uploaded a fix for this bug last night on NuGet Gallery. You can download it here: https://www.nuget.org/packages/Oracle.ManagedDataAccess.Core/
Works great, thanks Alex!
If you're only pulling in Oracle.EntityFramework.Core, it's probably grabbing the minimum version of Oracle.ManagedDataAccess.Core that it requires, which is where the bug is present. Go into NuGet and get Oracle.ManagedDataAccess.Core 2.19.91 specifically. That resolves the issue.