Devart Forums

Hi,
We are using Devart.UniDirect class (5.0.499.0, runtime v2.0.50727) to connect to Oracle database. We use Direct connection mode and do not specify any pooling. Recently, from time to time we started to get error ORA03114. Right now we think we limited the cause of the error to the network problems and looking into fixing that.
But I also found a strange behavior. If I open the application and do some operation with the database, then take out my network cable (so I'm not in the network anymore), after that try to repeat the operation, I'm not getting the error in the moment when I call "connection.Open()", rather when I try to execute SQL command. In this moment I'm getting ORA-03114, but connection state shows as Open. How can I check that my server is available in the moment when I'm trying to open the connection?

Thank you,
Galina

We have reproduced the issue. We will investigate it and notify you about the results as soon as possible.

Do you have any news about this issue?

Thank you

We have implemented the Validate Connection parameter of the connection string for the Devart inner providers. If this parameter is set to true, all connections taken from the pool will be validated. For more information, please refer to http://www.devart.com/dotconnect/univer ... tring.html

We will post here when the corresponding build of dotConnect Universal is available for download.

The new build of dotConnect Universal 3.40.388 is available for download now!
It can be downloaded from http://www.devart.com/dotconnect/univer ... nload.html (trial version) or from Registered Users' Area (for users with valid subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?t=26904

Hi,
I'm using DotConnect for Oracle 6.10 and I have some ORA03114...
Can I have the same issue that above which concerned dot connect Universal?
Thanks

FredFred wrote:I'm using DotConnect for Oracle 6.10 and I have some ORA03114...

Try setting the connection string parameter "Validate Connection=true;" to validate connections that are being got from the pool. For more information, please refer to http://www.devart.com/dotconnect/oracle ... ction.html

The "Validate Connection=true;" connection string parameter was added in dotConnect for Oracle 6.0.58 and it is available in dotConnect for Oracle 6.10.

FredFred wrote:Can I have the same issue that above which concerned dot connect Universal?

If you use "provider=Oracle" parameter in connection string, then dotConnect Universal will use dotConnect for Oracle for working with Oracle. This means, such error can also occur when using dotConnect Universal. The Validate Connection connection string parameter was added to dotConnect Universal in the version 3.40.388. As we have written above, adding "Validate Connection=true;" to the connection string should fix the issue.