You have created the JDBC Provider and created alias and Datasource .You are Testing the Connection
If you are getting NameNotFoundException in the SystemOut.log that means there is JNDI lookup problem check Namespace lookup that are mentioned in the Code and config file's as mentioned in Previous post
If you are getting the SQLException Problem is either userid and password passes in J2C Authentication alias ,make sure the valid userid and password are passed.
If you are getting the java.lang.UnsatisfiedLinkError ,
1.If you are using Type2 or Type3 driver and getting java.lang.UnsatisfiedLinkError
This means JVM is unable to Load a native libraries that are needed by JDBC driver to
Resolve this check DataBase Home and library paths are correct
(ex:Oracl_Home,LIBPATH)
2.connecting user has proper permissions to access Native libraries
3.32-bit native libraries cannot be used with 64-bit application server JVM and vice
verse.Mismatches between the two can also cause java.lang.UnsatisfiedLinkError
If you are getting java.sql.SQLException: [IBM][SSLServer JDBC Driver][SQLServer]Could not find stored procedure 'master..xp_jdbc_open'. The problem is with stored procedure for JTA are not installed on the SQL ServerDatabase.these Stored procedures are required for XA connections.
If you are typical error messages like
DSRA8040I: java.sql.SQLException: IOException:The Network Adapter could not establish the connection
DSRA0010E: SQL State=null, Error code=17,002
Then try to connect to the database server using a stand alone java program to determine if you are able to connect successfully with the same properties that you have set in your Data Source outside the WebSphere Application server then Go with other possible Trouble shooting Technics .if it is giving same error out side WebSphere Application Server it is not related to WebSphere Application Server Coordinate with DBA Team to Resolve the Issue.
If you are getting NameNotFoundException in the SystemOut.log that means there is JNDI lookup problem check Namespace lookup that are mentioned in the Code and config file's as mentioned in Previous post
If you are getting the SQLException Problem is either userid and password passes in J2C Authentication alias ,make sure the valid userid and password are passed.
If you are getting the java.lang.UnsatisfiedLinkError ,
1.If you are using Type2 or Type3 driver and getting java.lang.UnsatisfiedLinkError
This means JVM is unable to Load a native libraries that are needed by JDBC driver to
Resolve this check DataBase Home and library paths are correct
(ex:Oracl_Home,LIBPATH)
2.connecting user has proper permissions to access Native libraries
3.32-bit native libraries cannot be used with 64-bit application server JVM and vice
verse.Mismatches between the two can also cause java.lang.UnsatisfiedLinkError
If you are getting java.sql.SQLException: [IBM][SSLServer JDBC Driver][SQLServer]Could not find stored procedure 'master..xp_jdbc_open'. The problem is with stored procedure for JTA are not installed on the SQL ServerDatabase.these Stored procedures are required for XA connections.
If you are typical error messages like
DSRA8040I: java.sql.SQLException: IOException:The Network Adapter could not establish the connection
DSRA0010E: SQL State=null, Error code=17,002
Then try to connect to the database server using a stand alone java program to determine if you are able to connect successfully with the same properties that you have set in your Data Source outside the WebSphere Application server then Go with other possible Trouble shooting Technics .if it is giving same error out side WebSphere Application Server it is not related to WebSphere Application Server Coordinate with DBA Team to Resolve the Issue.
No comments:
Post a Comment