Executing a Long Running Query with CommandTimeOut set in a .NET Application using ODP Fails With: Exception: System.AccessViolationException
(Doc ID 1317550.1)
Last updated on MAY 23, 2013
Applies to:Oracle Data Provider for .NET - Version 10.2.0.2 and later
***Checked for relevance on 22-May-2013***
Executing a long running query with CommandTimeOut set in a .NET application using ODP may fail with:
Message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
The top of the StackTrace may look similar to the following:
at Oracle.DataAccess.Client.OpsSql.Timeout(OpoSqlValTimeoutCtx& opoSqlValTimeoutCtx)
at Oracle.DataAccess.Client.OracleCommand.Timeout(Object state)
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
Upgraded the Oracle Data Provider for .NET to version 10.2.0.2.20
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document