4
無效的參數
服務器1：DMGR服務器（6.1版本）WebSphere測試連接失敗java.sql.SQLException中：在callDSRA0010E
服務器2：6.1安裝並作爲應用程序服務器的節點（ojdbc14.jar文件複製使用到這個服務器）
服務器3：甲骨文10gR2中安裝和聽衆和TNS是設置正確
我做了什麼：
- 創建在T的用戶（appli_01）他的數據庫wasdb02在server3處被解除。
- telnet server3 1521 from server2以及server1成功。
- 創建一個JAAS - 與別名= SAMPLE1用戶名= appli_01 J2C認證別名（數據庫的用戶名）密碼=該數據庫用戶
- 創建JDBC提供
創建一個數據源和得到的值作爲密碼如下
JNDI name :jdbc/sample1 Component-managed authentication alias : sample1 URL = jdbc:oracle:thin:@server3:1521:wasdb02然後保存並同步更改。
，最後如果我點擊測試連接，我得到以下錯誤：
測試連接操作在與下面的異常節點server3Node03失敗數據源SAMPLEDB在服務器節點代理：java.sql.SQLException中： callDSRA0010E中的參數無效：SQL State = null，錯誤代碼= 17,433。查看JVM日誌以獲取更多詳細信息。
和systemout日誌如下。
10/7/13 15:02:00:482 IST] 000011d5 DataSourceCon E DSRA8040I: Failed to connect to the DataSource. Encountered "": java.sql.SQLException: invalid arguments in callDSRA0010E: SQL State = null, Error Code = 17,433
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:145)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:190)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:286)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:250)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:441)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:839)
at oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:389)
at oracle.jdbc.xa.client.OracleXADataSource.getPooledConnection(OracleXADataSource.java:557)
at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:177)
at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:163)
at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:112)
at com.ibm.ws.rsadapter.DSConfigurationHelper$1.run(DSConfigurationHelper.java:1137)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.rsadapter.DSConfigurationHelper.getPooledConnection(DSConfigurationHelper.java:1132)
at com.ibm.ws.rsadapter.DSConfigurationHelper.testConnectionForGUI(DSConfigurationHelper.java:2355)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at com.ibm.ws.management.DataSourceConfigHelperMBean.testConnectionToDataSource2(DataSourceConfigHelperMBean.java:532)
at com.ibm.ws.management.DataSourceConfigHelperMBean.testConnection(DataSourceConfigHelperMBean.java:460)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:62)
at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:265)
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1089)
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:971)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802)
at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1055)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:948)
at com.ibm.ws.management.connector.AdminServiceDelegator.invoke(AdminServiceDelegator.java:139)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at com.ibm.ws.management.connector.soap.SOAPConnector.invoke(SOAPConnector.java:338)
at com.ibm.ws.management.connector.soap.SOAPConnector.service(SOAPConnector.java:204)
at com.ibm.ws.management.connector.soap.SOAPConnection.handleRequest(SOAPConnection.java:55)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:680)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:484)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1498)
我以前在WebSphere 6.1中經常遇到這種情況，只能通過重新啓動節點代理程序和服務器進程來解決問題。這可能不是你的問題，但它可能值得一試。 –
嗨迪斯科，它很酷..在節點代理程序重新啓動它很好地工作.. 非常感謝您的及時幫助。 – Christopher
@ Disco3考慮將您的評論添加爲答案，因爲它解決了克里斯托弗的問題，所以這是問題的正確答案。順便說一句，我有這個相同的問題，你的解決方案幫助我解決它。 –