String Title XA Interface SQLCA PID9086 Node000 SQLCODE 1403 To resolve these

String title xa interface sqlca pid9086 node000

This preview shows page 41 - 42 out of 349 pages.

String Title: XA Interface SQLCA PID:9086 Node:000 SQLCODE = -1403 To resolve these problems: 1. Correct your user name and password. If you specify your password on the GUI for the data source, ensure that the user name and password you specify on the bean are correct. The user name and password you specify on the bean overwrite whatever you specify when creating the data source. 2. Use the correct database name. 3. Rebind the packages (in the bnd directory) as follows: db2connect to dbname c:\SQLLIB\bnd>DB2 bind @db2ubind.lst blocking all grant public c:\SQLLIB\bnd>DB2 bind @db2cli.lst blocking all grant public 4. Ensure that the \WebSphere\AppServer\properties\wsj2cdpm.properties file has the right user ID and password. Error message java.lang.reflect.InvocationTargetException: com.ibm.ws.exception.WsException: DSRA0023E: The DataSource implementation class "COM.ibm.db2.jdbc.DB2XADataSource" could not be found. when trying to access a DB2 database One possible reason for this exception is that a user is attempting to use a JDBC 2.0 DataSource, but DB2 is not JDBC 2.0-enabled. This situation frequently happens with new installations of DB2 because DB2 provides separate drivers for JDBC 1.X and 2.0, with the same physical file name. By default, the JDBC 1.X driver is on the class path. To confirm this problem: v On Windows systems, look for the inuse file in the java12 directory in your DB2 installation root. If the file missing, you are using the JDBC 1.x driver. v On operating systems such as AIX or Linux, check the class path for your data source. If the class path does not point to the db2java.zip file in the java12 directory, you are using the JDBC 1.x driver. To correct this problem: v On Windows systems, stop DB2. Run the usejdbc2.bat file from the java12 directory in your DB2 instalation root. Run this file from a command line to verify that it completes successfully. v On operating systems such as AIX or Linux, change the class path for your data source to point to the db2java.zip file in the java12 directory of your DB2 installation root. CLI0119E System error. SQLSTATE=58004 - DSRA8100 : Unable to get a XAconnection or DSRA0011E: Exception: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0119E Unexpected system failure. SQLSTATE=5800 If you encounter this error when attempting to access a DB2 Universal Database (UDB) data source: 1. On the data source properties page in the administrative console, verify that the correct database name is specified on the data source. 2. On the custom properties page, check your user name and password custom properties. Verify that they are correct. 3. Ensure the user ID and password do not contain any blank characters, before, in between, or after. 4. Check that the WAS.policy file exists for the application, for example, D:\WebSphere\AppServer\ installedApps\markSection.ear\META-INF\was.policy .
Image of page 41
Image of page 42

You've reached the end of your free preview.

Want to read all 349 pages?

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture