Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Problem creating JDBC datasource

756 views
Skip to first unread message

eoin...@fmr.com

unread,
Jul 31, 2008, 7:01:56 AM7/31/08
to
I am trying to create a JDBC datasource through the Websphere V6.1 admin console. I have created the Datasource and the JAAS - J2C authentication data for it but when i try to test the connection i get this error.

java.sql.SQLException: invalid arguments in callDSRA0010E: SQL State = null, Error Code = 17,433.

I think this error has to do with the Authentication data, I get the same error if i test the connection with no authentication data added. I have created the same datasource on my local machine and it runs fine.

The only difference I can see on this server is that there are 2 Nodes. I create the Datasource on the node containing the server. How ever when i create the Authentication data, it adds the prefix for the other node.

Could the datasource be not finding the Authentication data because it is created in the scope of a different node. Is there any way of setting the scope of JAAS - J2C Authentication data to the correct node?

paul....@ie.ibm.com

unread,
Aug 1, 2008, 7:12:38 AM8/1/08
to
Hi ed7890,

"I create the Datasource on the node containing the server. How ever when i create the Authentication data, it adds the prefix for the other node."

When creating a new authentication data entry and specifying an alias, be aware that the node name is automatically appended as a prefix to the alias name you specify. For example, if you specify the alias, tek_test_Con3, and the node is MyNode, then the final alias name is: MyNode/tek_test_Con3.

So make sure that you are creating the J2C Authentication data on the same Server as the datasource is defined. It looks like you have them mixed up.

Fearo

thiago.z...@hsbcglt.com.br

unread,
Aug 1, 2008, 1:16:47 PM8/1/08
to
Hi, restart the nodeagent of the node where you configured the DataSource and then try the test connection again, I had the same error a bunch of times and the node restart always fix it.
0 new messages