Resolving problems when using databases

This section describes solutions to the following common problems that can arise when using databases:

You get error message BIP2322 with SQL State 40001

You get DB2 error message SQL0805N

You get DB2 error message SQL0998N

You get DB2 error message SQL1040N

  1. Scenario: You are using DB2, and you get message BIP2322 with SQL1040N.
  2. Explanation: The following DB2 message indicates that the value of the DB2 database configuration parameter maxappls has been reached:
    "SQL1040N The maximum number of applications is already connected to the database.
    SQLSTATE=57030"

    DB2 has rejected the attempt to connect.

    If this database is one of the defined broker databases, implying that a broker thread connection request has failed, the broker is probably not functioning correctly.

  3. Solution:
    1. Stop all brokers that connect to the affected database.
    2. Increase the value of the maxappls configuration parameter. Also, check the value of the associated parameter maxagents and increase it in line with maxappls.
    3. Restart the DB2 database.

You get DB2 error message SQL1224N when connecting to DB2

You get DB2 or ODBC error messages on z/OS

You do not know how many database connections a broker requires

You want to use XA with DB2

You get an XA coordination failure with DB2 V8 Fix Pack 2

You get error message BIP2322 when accessing DB2 on z/OS

On Oracle, a database operation fails to return any rows, even though the rows exist

You get a memory leak from the Oracle Client Interface on HP-UX 11

You get error message BIP2731 when using retained publications with a Sybase database

Database updates are not committed as expected

Related tasks
Database security
Is there a problem with a database?
ODBC tracing
Dealing with problems

Related reference
mqsicreatebroker command
mqsideletebroker command
Database facilities