Oracle RAC JDBC connection

Hi,

We're trying to install TS but got stuck in Common Services connection to the database.

TS Version : 7.3.1
OS : Windows 2008 R2 Enterprise SP1
Database : Oracle 11g RAC

We have followed the URL pattern as specified in Web Solutions Authoring Components 7.3 Installation Guide Revision 1 - page 58.

Our URL is:
jdbc Smiley Surprised

racle:thin@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=ip1)(PORT=1521)(ADDRESS=(PROTOCOL=TCP)(HOST=ip2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=)))

But it throws us the error below everytime :
java.sql.SQLException: Invalid Oracle URL specified

Can anybody tell me what is wrong with my URL? I can't proceed with the installation from here.

Thank You!

Find more posts tagged with

Comments

Adam Stoller

(a) search the forums
(b) check with Support

I seem to recall someone else posting about something like this and indicating Support had helped them through because there was a bug in the installer with regard to dealing with Oracle RAC. It might have been a different-but-similar issue, but checking with Support is still a recommended procedure.

jihan

Hi,

The forum earlier about the bug for Oracle RAC is because it keeps returning null message even when you have point to a correct database & driver.
Had this problem before, worked with Support to resolve it. It's fine now.

Just managed to solve the URL issue - it needs another parameter : LOAD_BALANCER=on.

Managed to go up til the end of the configuration, but TS installation ended up Unsuccessful. I've posted another thread on this:

http://devnet.interwoven.com/forums_vb/showthread.php?t=37332&forumid=11
TeamSite installation unsuccessful

Perhaps you can help me with this?

Thank You.

Witty

Two of the classes in the installer are not correctly parsing the fields when Oracle RAC or Custom is chosen for the DB type. Contact autonomy support so that they can provide you with a zip file with files in it. You will have to rebuild the .iwpkg file and regenerate the MD5 sum checkfile.

We have encountered this issue and I'm sure contacting support will fix it.