MustGather: Database connections or connection pooling problems for all releases of V4.0 and V5.0

Technote (FAQ)
Problem
MustGather for problems with the WebSphere® Application Server Database Connections/Connection Pooling component for all releases of V4.0 and V5.0. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
Solution
If you have already contacted support, continue on to the component-specific MustGather information. Otherwise, click: MustGather: Read first for all WebSphere Application Server products.


DB Connections/Connection Pooling specific MustGather information
The following additional documentation must be provided when submitting Database Connections/Connection Pooling PMRs:
  1. WebSphere Application Server version and platform.

  2. List of all interim fixes applied or collect the following files:
    • product.xml file for WebSphere Application Server V4 located in the following directory:

      install_root/properties/com/ibm/websphere

    • event.history file for WebSphere Application Server V5 located in the following directory:

      install_root/properties/version/history

  3. Name and exact version of the JDBC Driver (for example: Oracle Thin JDBC Driver version 9.2.0.4.0)

  4. stderr and stdout log files from the Application Server.
    • For releases of WebSphere Application Server V4.0:

      install_root/logs

    • For releases of WebSphere Application Server V5:

      install_root/logs/server1

  5. activity.log file located in the following directory:

    install_root/logs

  6. What is the database error code (if any) (for example: SQL0129E, ORA-01000)?

    Have you checked the database documentation for the error description and performed the recommended action accordingly?

  7. What is the exception?

  8. If using DB2®, run the db2level command (on both client and server) and collect the output.

  9. Follow instructions tosend diagnostic information to IBM support.


For Connection Pooling Problems
  1. Does the application use a WebSphere data source?

  2. Name of the data source that has the problem.

  3. XMLConfig export for WebSphere Application Server V4.

  4. variables.xmlandresources.xml files for WebSphere Application Server V5 located in the following directory:

    install_root/config

  5. Detailed description of application topology and the problem scenario when it occurs.

  6. Have you tried the same functionality using the JDBC Driver directly? If yes, does the problem occur?

  7. For WebSphere Application Server V5, does the application use the WebSphere Application Server V4 or V5 data source?

  8. Follow instructions tosend diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to the Database Connections/Connection Pooling component, search the WebSphere Application Server support site.
Related information
Submitting information to IBM support

Steps to getting support

MustGather: Read first

Troubleshooting guide












Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, DB Connections/Connection Pooling
Operating system(s): AIX, HPUX, Linux, Multi-Platform, Solaris, Windows
Software version: 3.5, 4.0, 5.0, 5.1, 6.0
Software edition: Edition Independent
Reference #: 1153297
IBM Group: Software Group
Modified date: 2004-12-08