Another option would be to update your jdbc connection to use the mulitple
hosts (I am not an expert with this, but we use a rac as well)  Here is an
example based on one of our 2 node racs (more nodes just has more host
entries):

jdbc:oracle:thin:@
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=A0361)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=A0362)(PORT=1521))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=A036)(FAILOVER_MODE=(TYPE=SELECT)(METHOD=BASIC)(RETRIES=180)(DELAY=5))))

On Fri, Apr 3, 2009 at 4:13 PM, Lyle Taylor <[email protected]> wrote:

> **
>
> Thanks, all for your help.  I finally figured out what the deal was.
>
>
>
> So, the issue was due to the fact that we are using an Oracle RAC which has
> multiple database servers hitting the same database for redundancy.  The
> issue is that, while for most clients, the service name is the service name,
> for jdbc, it wants to specify the SID which appears to correspond to the
> Session ID in the RAC.  In our case, the normal service name is A036, and
> normal clients can use that just fine.  However, when jdbc goes and hits the
> server, it specifies a SID of A036, which the instance in the RAC that it’s
> hitting doesn’t expect.  It turns out that, where we have two servers in the
> RAC, the Session IDs for the servers are A0361 and A0362.  So, in the end, I
> had to specify A0361 instead of A036.
>
>
>
> In addition, BMC’s install guide mentions that the service name and
> computer name need to be the same in tnsnames.ora.  In this case, that is
> not correct, and cannot be set up that way.  The issue is that, while jdbc
> needs A0361 to be able to connect, the processes that actually do the
> database updates don’t use jdbc and can connect normally using A036.  This
> has the effect that the installer needs one value to check the status of the
> database, and then the subprocess that updates the database needs another
> value.  To handle that situation, I had to change the tnsnames.ora file so
> that it was like this:
>
>
>
> A0361 = (…. (SERVICE_NAME=A036)
>
>
>
> That way, the Java installer could test the database using A0361, and then
> when the subprocess came along and tried to connect to A0361, it would get
> properly directed to A036, which it can use.
>
>
>
> Thanks again.
>
> Lyle
>
>
>
>
>
> NOTICE: This email message is for the sole use of the intended recipient(s)
> and may contain confidential and privileged information. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not the
> intended recipient, please contact the sender by reply email and destroy all
> copies of the original message.
> __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"

Reply via email to