RE: RAC behavior - with Oracle JDBC Thin Driver - is this expected behavior?
- From: "Pradeep Chetal" <Pradeep.Chetal@xxxxxxxxxxxxxx>
- To: <jobmiller@xxxxxxxxx>, <sjaffarhussain@xxxxxxxxx>
- Date: Wed, 11 Feb 2009 14:25:33 -0500
That's a good article but for WL 10.3/Oracle 11g. We are still on way
old WL 8.1
Thanks,
-- Pradeep
-----Original Message-----
From: Job Miller [mailto:jobmiller@xxxxxxxxx]
Sent: Wednesday, February 11, 2009 6:43 AM
To: Pradeep Chetal; sjaffarhussain@xxxxxxxxx
Cc: Oracle L
Subject: Re: RAC behavior - with Oracle JDBC Thin Driver - is this
expected behavior?
assuming you are using weblogic and connection pools, you'll want to
read this:
http://www.oracle.com/technology/products/weblogic/OracleWLS_RAC.pdf
--- On Wed, 2/11/09, Syed Jaffar Hussain <sjaffarhussain@xxxxxxxxx>
wrote:
> From: Syed Jaffar Hussain <sjaffarhussain@xxxxxxxxx>
> Subject: Re: RAC behavior - with Oracle JDBC Thin Driver - is this
expected behavior?
> To: Pradeep.Chetal@xxxxxxxxxxxxxx
> Cc: "Oracle L" <oracle-l@xxxxxxxxxxxxx>
> Date: Wednesday, February 11, 2009, 12:39 AM
> TAF callbacks (FAILOVER_MODE) doesn't supported by JDBC
> connections. In
> order to implement failover with JDBC thin connections, you
> need to
> implement FCF (fast connection failover).
> Following are the few references that might help you to
> configure FCF for
> your JDBC connection failover:
>
>
> Note
>
433827.1<https://metalink2.oracle.com/metalink/plsql/showdoc?db=NOT&id=4
33827.1&blackframe=1>
> How
> To Verify And Test Fast Connection Failover Setup From a
> JDBC Thin Client
>
http://download.oracle.com/docs/cd/B19306_01/java.102/b14355/fstconfo.ht
m#CIHJBFFC
>
> Regards,
>
> Jaffar
>
> On Wed, Feb 11, 2009 at 3:42 AM, Pradeep Chetal <
> Pradeep.Chetal@xxxxxxxxxxxxxx> wrote:
>
> >
> >
> > Hi,
> >
> >
> >
> > We have a Java based app that runs with Weblogic and
> oracle 10gr2 as the
> > DB.
> >
> >
> >
> > We use the following for the RAC string for JDBC
> connection
> >
> >
> >
> > *RAC_STRING = *
> >
> > * jdbc:oracle:thin:@(DESCRIPTION=** *
> >
> > * **(FAILOVER=ON)*
> >
> > * (LOAD_BALANCE=ON)*
> >
> > *
> (ADDRESS=(PROTOCOL=TCP)(HOST=dingo)(PORT=1521))*
> >
> > * (ADDRESS=(PROTOCOL=TCP)(HOST=wolf)(PORT=1521))*
> >
> > * (CONNECT_DATA=(SERVICE_NAME=msmdb)))*
> >
> > * *
> >
> > * *
> >
> > We use this with a 2-node RAC and all the API calls
> to our application are
> > sort of evenly distributed between the 2 nodes.
> >
> >
> >
> > Now if for some reason, node 1goes down, we see that
> NOT all the new API
> > calls go to node-2 RAC. Some of them are lost until we
> re-start the
> > application.
> >
> >
> >
> > I thought the RAC_STRING will be dynamic and will NOT
> send calls to node 1
> > if it is down.
> >
> >
> >
> > Are we missing any configuration parameters here?
> >
> >
> >
> > Thanks,
> >
> >
> >
> > -- Pradeep
> >
> >
> >
> > *Pradeep Chetal*
> > Sr. Director - Infrastructure Architecture
> > ------------------------------
> > *Mformation Technologies Inc.*
> > *Switchboard:* +1 732 692 6200
> >
> > ------------------------------
> >
> > Visit MFORMATION <http://www.mformation.com>at
> MWC in Barcelona, Hall 1
> > Booth A56, Mobile World Congress 2009
> >
> <http://www.mobileworldcongress.com/homepage.htm>and
> see how the
> > MFORMATION SERVICE MANAGER can help you to transform
> your business.
> >
> > Please consider the environment before printing
> >
> >
>
>
> --
> Best Regards,
>
> Syed Jaffar Hussain
> Oracle Certified Master (10g)
> http://www.oracle.com/technology/ocm/shussain.html
> Oracle ACE
>
http://apex.oracle.com/pls/otn/f?p=19297:4:1579866181463918::NO:4:P4_ID:
126
> OCP 8i,9i & 10g DBA
> RAC Certified Expert
> Official Oracle RAC SIG Representative for Saudi Arabian
> region (
> http://www.oracleracsig.org/)
> I blog at
> http://jaffardba.blogspot.com/
> --------------------
> "Winners don't do different things. They do things
> differently."
--
//www.freelists.org/webpage/oracle-l
Other related posts:
