WebSphere Adapter for JDBC

Troubleshooting the tutorial

When using the tutorial, you need to take action if the adapter fails to start up or if the adapter fails during processing.

  1. The adapter could fail to start up. If this happens, see the adapter message status log file to find the cause of the failure.
    Common reasons why the adapter would fail to start up are listed here.
    Table 1. Common reasons for adapter start-up failure
    Error Cause
    Driver class does not exist. The database driver JAR file does not exist in the runtime's lib folder.
    Logon error; invalid username/password. The authentication alias does not have the correct username or password for connecting to the database.
  2. The adapter could fail during processing. If this happens, see the adapter message status log file to find the cause of the failure.
    Common reasons why the adapter could fail during processing are listed here.
    Table 2. Common reasons for adapter failure during processing
    Error Cause
    Primary key does not exist. The table does not have a primary key defined; thus, the PrimaryKey application-specific information on the business object is not set to true.
    A record with the primary key already exists. The record already exists in the database. Insert a record with a primary key that does not exist in the database.

Terms of use |

Last updated: Tue 12 Dec 2006 03:32:39

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)