If your application displays JDBC-related exception messages, activate the JDBC trace service. The resulting log text can help you identify the problem.
Turn on tracing for most database JDBC implementations
through the administrative console; see the article Enabling trace at server startup for
instructions.
Turn on tracing for most database JDBC
implementations through the administrative console; see the articleTracing and logging configuration for
instructions.
Set trace for the previously mentioned JDBC drivers through data source custom properties. For example, use custom property spyAttributes to enable the JDBC trace for SequeLink or Connect JDBC drivers. Consult your driver documentation for details on the custom property that enables trace for your JDBC implementation.
If the JDBC tracing service cannot help you isolate and fix your problem, consult the IBM Support website for WebSphere Application Server at http://www.ibm.com/support/search.wss?rs=180&tc=SSEQTP&tc1=SSCMP9Y. Use the site search function to find current information on known problems and their resolutions. Locating the right troubleshooting tip can save time that, otherwise, you might spend on opening and tracking a PMR.
Learn about other IBM Support options in the articles Diagnosing and fixing problems: Resources for learning and Troubleshooting help from IBM.