Synesso
Synesso

Reputation: 38978

JDBC URL for Oracle XA client

Using the JDBC driver oracle.jdbc.xa.client.OracleXADataSource, what is the correct format of the JDBC URL? The thin format of

jdbc:oracle:thin:@host:port:sid 

does not work. WebSphere is reporting that the given url (which is otherwise correct) is invalid.

The test connection operation failed for data source Oracle MyDB (XA) on 
server nodeagent at node MY_node with the following exception: 
java.sql.SQLException: Invalid Oracle URL specifiedDSRA0010E: SQL State = 99999, 
Error Code = 17,067. View JVM logs for further details.

There is nothing in the JVM logs.

Upvotes: 5

Views: 13345

Answers (6)

Amit Sharma
Amit Sharma

Reputation: 1

if you are doing using wsadmin command then you need to stop manager,stop node,start manager, sync node and then start node (I mean full sync). Hopefully this will resolve the issue. I dont know why but this resolves my issue.

Upvotes: 0

Eduard Korenschi
Eduard Korenschi

Reputation: 236

Had the same issue. Dont know about simple deployments, but on a two nodes cluster, I restarted the first node, and the connection started working on it (not on the second). Restarted the second node, and the connection started working there too.

So just restart the nodes (I also restarted the nodeAgents, but i don't know if it's necessary).

Upvotes: 0

vishnu viswanath
vishnu viswanath

Reputation: 3854

For me the issue resolved by adding alias name, username and password in JAAS - J2C authentication data. And also selecting this entry as Component-managed authentication alias.

Upvotes: 5

Alex
Alex

Reputation: 21

In my case, the problem went away when I change the authentication property of the jdbc resource reference from Authentication=Application to Authentication=Container

Upvotes: 2

Pascal Thivent
Pascal Thivent

Reputation: 570345

Whether you use a XA Driver or not, the JDBC connection string is the same (and the format of your question is correct).

Upvotes: 5

Synesso
Synesso

Reputation: 38978

In case this happens to anyone else. The problem went away after restarting websphere.

Upvotes: 3

Related Questions