Re: dataguard connection question

From: Joan Hsieh <joan.hsieh_at_tufts.edu>
Date: Tue, 09 Jun 2009 12:22:08 -0400
Message-ID: <4A2E8C30.2070506_at_tufts.edu>



Thanks Dick,

Do you mean the second host to xythdb-02? How about SERVICE_NAME? is always XYTHT1?

Thanks, --joan

 > jdbc:oracle:thin:_at_(DESCRIPTION=(
 >
 > ADDRESS=(PROTOCOL=tcp)(HOST=test-xythdb-01.uit.tufts.edu)(PORT=11003)
 >
 > address=(protocol=tcp)(host=test-xythdb-01.uit.tufts.edu)(PORT=11003))
 >      (CONNECT_DATA=(SERVICE_NAME=XYTHT1))) JDBCConnectionPool:395

  jdbc:oracle:thin:_at_(DESCRIPTION=(

  ADDRESS=(PROTOCOL=tcp)(HOST=test-xythdb-01.uit.tufts.edu)(PORT=11003)  > address=(protocol=tcp)(host=test-xythdb-02.uit.tuft.sedu) PORT=11003)) ?

Goulet, Richard wrote:

> Joan,
>
> Your biggest difficulty here is JDBC because it does not use the
> Oracle SQL*Net layer thereby making this a touch difficult. The
> following is something I pulled (in spirit only) from another project I
> worked on that had a requirement for a standby database & no manual
> intervention on the app side:
>
> jdbc:oracle:thin:_at_(DESCRIPTION=(
>
> ADDRESS=(PROTOCOL=tcp)(HOST=test-xythdb-01.uit.tufts.edu)(PORT=11003)
>
> address=(protocol=tcp)(host=test-xythdb-01.uit.tufts.edu)(PORT=11003))
> (CONNECT_DATA=(SERVICE_NAME=XYTHT1))) JDBCConnectionPool:395
>
> It helped in that setup and did work flawlessly, but yours may be
> different. Alternatively you might consider setting up a connection
> manager somewhere in your infrastructure. It can handle just this type
> of problem, but it's another layer of indirection.
>
> Dick Goulet
> Senior Oracle DBA
> PAREXEL International
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Joan Hsieh
> Sent: Monday, June 08, 2009 7:35 PM
> To: oracle_l
> Subject: dataguard connection question
>
> Hi List,
>
> I have question regarding dataguard, the primary database is xytht1, the
>
> standby is xytht2. the oracle is 11.1.0.7. Our client is using jdbc thin
>
> client to connect the primary database. the connection string is
>
> jdbc:oracle:thin:_at_(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=test-xythdb-
> 01.uit.tufts.edu)(PORT=11003))(CONNECT_DATA=(SERVICE_NAME=XYTHT1)))
> JDBCConnectionPool:395
>
> After I tested switchover, the client lost connection, and have to
> manually reconfigure to change the HOST and service name. This is not
> acceptable to our client. I have no knowledge on how to automatically
> switchover/failover for the client jdbc connection. Do you have any
> ideas on this? Thank you for any helps.
>
> Joan
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Tue Jun 09 2009 - 11:22:08 CDT

Original text of this message