Implement RAC ourselves

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
Post Reply
Posts: 34
Joined: Wed 29 Sep 2010 11:27

Implement RAC ourselves

Post by bmarotta » Fri 02 Mar 2012 10:44


we are running Oracle on a RAC and using Direct Mode. Currently we have the problem that if the node we are connecting is not available, we have to manually config the ConnectionStrings in the configs and restart all our services.

We were thinking about having one connection string for each RAC server (currently 2) so that we can switch without having to change the configs. To implement this we have to first be able to identify if a node is alive and second do it always before opening a connection.

The problem is that the Devart Connection Pool is a black box. When using a Context, one never knows when the connection is open and if an error happens in the opening of the connection, it is already too late for switching the Connection String.

Would you have any suggestion how we can intelligently "ping" the servers to know which is the master one, before opening the connections and also without adding too much overhead to the DB communication?

Best regards,

Bruno Marotta

Devart Team
Posts: 2192
Joined: Wed 02 Nov 2011 09:44

Post by Pinturiccio » Mon 05 Mar 2012 11:49

Its not possible to identify whether a node is alive in dotConnect for Oracle before opening a connection. You can only open a connection to one node, and if it throws an exception, handle it and try connecting to another node.

Post Reply