Re: Connecting to a RAC instance using JDBC:thin driver

  • From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
  • To: Steve Wales <sjwales@xxxxxxxxxxx>
  • Date: Wed, 5 Dec 2012 07:37:23 +0000

Which database and jdbc version? I believe that with recent releases of
jdbc drivers you can use scanname:port:servicename in your jdbc connect
string. There's an interoperability table in (I think) the 11.2 docs on
scan configuration. On the other hand it sounds like the rationale for RAC
may be a bit off. In general RAC isn't an HA but a scalability solution
(because you only have the one database), arguably RAC systems suffer
*more* downtime than single server systems due primarily to the increased
complexity of the setup.
On Dec 4, 2012 10:59 PM, "Steve Wales" <sjwales@xxxxxxxxxxx> wrote:
> We support an ERP application that uses the jdbc thin client to connect to
> Oracle Databases.
> Historically it's just been done using a single instance of a database and
> the connect string looks something like this:
> One customer for this vendor decided that they wanted to use RAC for their
> Prod database for the failover protection.
> We put together the connect string (which works as a valid connect string
> when not used in this app startup scripting) as so:
> jdbc:oracle:thin:@
> OL=TCP)(
> It's running on a Linux environment.
> The wrapper scripting for the startup of the application infrastructure
> doesn't support parentheses because no one at the vendor had ever
> considered
> RAC as an option.
> Is there a way to pass through a connect string to a RAC database, via the
> jdbc thin client without using parentheses in the connect string.
> (We have tried escaping the parentheses and using double quotes but the way
> they have their infrastructure built, it just doesn't seem to want to work)
> Thanks
> Steve
> --
> //


Other related posts: