Our project recently updated to the newer Oracle.ManagedDataAccess DLL\'s (v 4.121.2.0) and this error has been cropping up intermittently. We\'ve fixed it a few times with
upgrade Oracle.ManagedDataAccess.dll to version 4.122.1.0 solved. If you are using vs 2017, we can update via NuGet.