OCI connections and Oracle client dependencies
Posted: Mon 29 Apr 2013 10:16
My company is using dotConnect for Oracle to phase out use of Oracle ODAC for Windows client (and associated problems with it) on a range of asp.net applications. We have a problem however, because our Oracle production servers are configured for failover and our database administrators do not want us to use direct connections.
If we use OCI based connections, what other software is required on our IIS servers? I am specifically worried that we will return to the same versioning problems we were seeing using Oracle ODAC for windows client. This is a big issue for us as we have multiple environments we need to deploy applications to, and we do not have control over our production and some of our testing environments (they are contracted out to a service provider).
Alternatively if we want to use direct connections, how can we provide for database failover? If transparent application failover is unavailable to us, is there something else we can do to allow some sort of failover ability?
If we use OCI based connections, what other software is required on our IIS servers? I am specifically worried that we will return to the same versioning problems we were seeing using Oracle ODAC for windows client. This is a big issue for us as we have multiple environments we need to deploy applications to, and we do not have control over our production and some of our testing environments (they are contracted out to a service provider).
Alternatively if we want to use direct connections, how can we provide for database failover? If transparent application failover is unavailable to us, is there something else we can do to allow some sort of failover ability?