Default Command Timeout of Oracle EF Driver

Discussion of open issues, suggestions and bugs regarding Entity Framework support in ADO.NET Data providers
Post Reply
GrMikeD
Posts: 22
Joined: Tue 10 Nov 2009 20:24

Default Command Timeout of Oracle EF Driver

Post by GrMikeD » Mon 30 Jun 2014 16:52

Hello, I have following two questions:

1) Which is the default command timeout of the Devart Oracle EF driver?

2) Is this accessed through ObjectContext.CommandTimeout of DbContext?

Thanks in advance!

Edit: The reason I ask is because a Devart Oracle query seems to freeze for ever when the database issues a ORA-12571: TNS:packet writer failure error. I am not sure if it is a matter of commandtimeout waiting infinitely, or an OracleDb issue, or a Devart driver issue...

Details: Oracle 11g, Devart for Oracle 8.3.146.6

Shalex
Site Admin
Posts: 8247
Joined: Thu 14 Aug 2008 12:44

Re: Default Command Timeout of Oracle EF Driver

Post by Shalex » Thu 03 Jul 2014 15:04

GrMikeD wrote:1) Which is the default command timeout of the Devart Oracle EF driver?

2) Is this accessed through ObjectContext.CommandTimeout of DbContext?
Command timeout is determined by the value of the OracleCommand.CommandTimeout property. Default value is 0 (no limit). You can control the value of OracleCommand.CommandTimeout via the Default Command Timeout connection string parameter.
If you set ObjectContext.CommandTimeout, its value will be assigned to OracleCommand.CommandTimeout before command execution.
GrMikeD wrote:Edit: The reason I ask is because a Devart Oracle query seems to freeze for ever when the database issues a ORA-12571: TNS:packet writer failure error.
Please send us a small test project with the corresponding DDL/DML script so that we can reproduce the issue in our environment.

Post Reply