RE: jdbc thin and TAF connections

  • From: Herring Dave - dherri <Dave.Herring@xxxxxxxxxx>
  • To: John Scoles <scoles@xxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 20 Apr 2011 16:00:34 +0000

Right, I don't have a good place to test this.  I was figuring a check of 
FAILOVER* columns in the GV$SESSION view would be good enough verification on 
what is getting set.  I also validated with using sqlplus with a full connect 
string:

sqlplus <user>/<pass>@'(DESCRIPTION...(FAILOVER = ON)...(FAILOVER_MODE = (TYPE 
= SELECT) (METHOD = BASIC))'

that indeed FAILOVER* columns were set properly in GV$SESSION, so I hopefully 
eliminated any other problem other than jdbc/10g combo.

DAVID HERRING
DBA
Acxiom Corporation
EML   dave.herring@xxxxxxxxxx
TEL    630.944.4762
MBL   630.430.5988 
1501 Opus Pl, Downers Grove, IL 60515, USA
WWW.ACXIOM.COM  

The information contained in this communication is confidential, is intended 
only for the use of the recipient named above, and may be legally privileged. 
If the reader of this message is not the intended recipient, you are hereby 
notified that any dissemination, distribution or copying of this communication 
is strictly prohibited. If you have received this communication in error, 
please resend this communication to the sender and delete the original message 
or any copy of it from your computer system. Thank you.


-----Original Message-----
From: John Scoles [mailto:scoles@xxxxxxxxxxx] 
Sent: Wednesday, April 20, 2011 10:45 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: jdbc thin and TAF connections

TAF is deep down on the OCI side of things so I think all clients 
support it if is enabled by the 'TNS entry' what I think jdbc/thin does 
not support it the TAF callback to java when an event happens as well I 
know that the thin client does not support service naming so that might 
be an issue as well
X-archive-position: 35849
X-ecartis-version: Ecartis v1.0.0
Sender: oracle-l-bounce@xxxxxxxxxxxxx
Errors-to: oracle-l-bounce@xxxxxxxxxxxxx
X-original-sender: scoles@xxxxxxxxxxx
Precedence: normal
Reply-To: scoles@xxxxxxxxxxx
List-help: <mailto:ecartis@xxxxxxxxxxxxx?Subject=help>
List-unsubscribe: <oracle-l-request@xxxxxxxxxxxxx?Subject=unsubscribe>
List-software: Ecartis version 1.0.0
List-Id: oracle-l <oracle-l.freelists.org>
X-List-ID: oracle-l <oracle-l.freelists.org>
List-subscribe: <oracle-l-request@xxxxxxxxxxxxx?Subject=subscribe>
List-owner: <mailto:steve.adams@xxxxxxxxxxxx>
List-post: <mailto:oracle-l@xxxxxxxxxxxxx>
List-archive: <//www.freelists.org/archives/oracle-l>
X-list: oracle-l

One way to test it is to loop over a simple select statement  (select 
sysdate from dual) with a java app and then shut down you db.

If TAF is working it should just hang (this depends on the timeout ) and 
then start up again when you start the DB.

Rather brute force but it does the job.

You have no test env so the point is Moot I guess?
cheers
> Folks,
>
> Just a warning up front on this question, I'm still only drinking java and 
> not coding in it nor having little to no understanding of how it's related to 
> the db.
>
> That said, we've got a 4-node RAC on 10.2.0.2 with thousands of incoming jdbc 
> thin connections coming in per hour.  The app team has sent me their connect 
> strings and I see they include "...(FAILOVER = ON)...(FAILOVER_MODE = (TYPE = 
> SELECT) (METHOD = BASIC))" and I've verified this in what's displayed in the 
> listener logs. Yet checking FAILOVER_TYPE and FAILOVER_METHOD in GV$SESSION I 
> see only "NONE".
>
> MOS note 297490.1 says that the 10g jdbc/thin driver doesn't support TAF, so 
> my assumption is this is why the physical connection drops all failover 
> definitions for jdbc.  Correct?  If so, then is the best option to define 
> this for the Oracle services they're connecting to via srvctl?  Currently we 
> have:
>
> % srvctl config service -d $db_unique_name -a
> service1 PREF: inst1 inst2 AVAIL:  TAF: NONE
> service2 PREF: inst3 inst4 AVAIL:  TAF: NONE
>
> I assume that if I give the Oracle service any definition that jdbc 
> connections will still pick them up, even if all TAF definitions are ignored 
> on their connect string.  Correct?  I'd test this to get my answer but I 
> don't have a test system and due to my ignorance with java, I couldn't get a 
> test jdbc connection working even after using MOS doc 433827.1.  Now if this 
> was COBOL-72...
>
> Thx.
>
> DAVID HERRING
> DBA
> Acxiom Corporation
> EML   dave.herring@xxxxxxxxxx
> TEL    630.944.4762
> MBL   630.430.5988
> 1501 Opus Pl, Downers Grove, IL 60515, USA
> WWW.ACXIOM.COM
>
> The information contained in this communication is confidential, is intended 
> only for the use of the recipient named above, and may be legally privileged. 
> If the reader of this message is not the intended recipient, you are hereby 
> notified that any dissemination, distribution or copying of this 
> communication is strictly prohibited. If you have received this communication 
> in error, please resend this communication to the sender and delete the 
> original message or any copy of it from your computer system. Thank you.
>
> --
> //www.freelists.org/webpage/oracle-l
>
>

--
//www.freelists.org/webpage/oracle-l


--
//www.freelists.org/webpage/oracle-l


Other related posts: