WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Resolving problems when using databases
Use the advice given here to help you to resolve problems that can arise when using databases.
Before you start:
- DB2 error message SQL0443N is issued
- DB2 error message SQL0805N is issued
- DB2 error message SQL0998N is issued on Linux
- DB2 error message SQL0998N or SQL1248N is issued
- DB2 error message SQL1040N is issued
- DB2 error message SQL1224N is issued when you connect to DB2
- DB2 or ODBC error messages are issued on z/OS
- You do not know how many database connections a broker requires
- You want to use XA with DB2 databases
- XA coordination fails if the database restarts while the broker is running
- Error message BIP2322 is issued when you access DB2 on z/OS
- Error message BIP2322 IM004 is issued when you connect to an Informix database
- On Oracle, a database operation fails to return any rows, even though the rows exist
- Broker commands fail when the Oracle 10g Release 2 client runs on Linux on POWER with Red Hat Enterprise Linux Advanced Server V4.0
- Error message BIP2322 Driver not capable is issued when you use an Informix database
- Database updates are not committed as expected
- You want to list the database connections that the broker holds
- The queue manager finds the XA resource manager is unavailable when configured for XA with DB2 on Windows
- Error messages are received when you are trying to remove a DB2 database on Windows when you are using a sample
- DB2 error message SQL7008N is issued
- SQLCODE -981 is issued when you access DB2 on z/OS
DB2 error message SQL0443N is issued
DB2 error message SQL0805N is issued
DB2 error message SQL0998N is issued on Linux
- Scenario: You are trying to use a globally coordinated message flow with DB2 on Linux and error message SQL0998N is issued with Reason Code 09 and Subcode " ".
- Solution: Check that the LD_ASSUME_KERNEL environment variable is not set. If it is set, use the unset command to remove it from your environment and ensure that you modify your profile scripts so that it remains unset.
DB2 error message SQL0998N or SQL1248N is issued
DB2 error message SQL1040N is issued
DB2 error message SQL1224N is issued when you connect to DB2
DB2 or ODBC error messages are issued on z/OS
You do not know how many database connections a broker requires
You want to use XA with DB2 databases
XA coordination fails if the database restarts while the broker is running
Error message BIP2322 is issued when you access DB2 on z/OS
Error message BIP2322 IM004 is issued when you connect to an Informix database
On Oracle, a database operation fails to return any rows, even though the rows exist
- Scenario: You are using Oracle databases in your message flows, and ESQL binds against columns that are declared as data type CHAR, and those parameter markers are referenced in a WHERE clause. The database operation fails to return any rows, even though the rows exist.
- Explanation: Fixed-length character strings must be padded with blank characters on Oracle for this type of comparison to succeed.
- Solution: Define the CHAR columns as VARCHAR2 columns, or pad the ESQL variable with blank characters to the required column length, so that the comparison locates the required rows from the table.
Broker commands fail when the Oracle 10g Release 2 client runs on Linux on POWER with Red Hat Enterprise Linux Advanced Server V4.0
Error message BIP2322 Driver not capable is issued when you use an Informix database
Database updates are not committed as expected
You want to list the database connections that the broker holds
- Scenario: You want to list the database connections that the broker holds.
- Solution: The broker does not have any functionality to list the connections that it has to a database. Use the facilities that your database supplies to list connections. Refer to the documentation for your database to find out how to perform this task.
The queue manager finds the XA resource manager is unavailable when configured for XA with DB2 on Windows
Error messages are received when you are trying to remove a DB2 database on Windows when you are using a sample
DB2 error message SQL7008N is issued
SQLCODE -981 is issued when you access DB2 on z/OS
- Scenario: You are running a message flow that uses ODBC database interaction. When a commit or rollback is attempted, DB2 reports an error with SQLCODE=-981 and SQLSTATE=57015. An error message is seen similar to: {DB2 FOR OS/390}{ODBC DRIVER}{DSN09015} DSNT408I SQLCODE = -981, ERROR: THE SQL STATEMENT FAILED BECAUSE THE RRSAF CONNECTION IS NOT IN A STATE THAT ALLOWS SQL OPERATIONS, REASON 00C12219
- Explanation: You can choose for ODBC database operations to be committed or rolled back irrespective of the success or failure of the message flow transaction as a whole. This error can be seen if you attempt to use more than one uncoordinated ODBC database connection on a single message flow thread.
- Solution: Only one uncoordinated ODBC database connection per thread is supported. Update your message flow to perform ODBC database operations outside of the message flow transaction on only one database. Any number of different databases are supported as part of a coordinated message flow transaction.