If your application displays JDBC-related exception messages,
activate the JDBC trace service. The resulting log text can help you
identify the problem.
Trace strings for JDBC data sources
Turn on tracing
for most database JDBC implementations through the administrative
console; see the article Enabling trace, for instructions.
This
method activates JDBC trace for all applications that run in the server
you specify. Identify your database type by selecting the trace group
WAS.database and typing one of the following trace strings in the
console:
- com.ibm.ws.database.logwriter Trace string for databases
that use the GenericDataStoreHelper. You can also use this trace
string for unsupported databases.
- com.ibm.ws.db2.logwriter Trace string for DB2® databases.
- com.ibm.ws.oracle.logwriter Trace string for Oracle databases.
- com.ibm.ws.derby.logwriter Trace string for Derby databases.
- com.ibm.ws.informix.logwriter Trace string for Informix® databases.
- com.ibm.ws.sqlserver.logwriter Trace string for Microsoft® SQL Server databases.
- com.ibm.ws.sybase.logwriter Trace string for Sybase databases.
A few JDBC drivers require that you set trace differently,
at the data source level. These drivers include:
- Microsoft SQL Server JDBC driver
- DataDirect Connect for JDBC driver for MS SQL Server
Configuring trace for these drivers through the WAS.database
group results in corrupt trace information. The application server
sets trace for the group at the server level, causing the trace service
to begin only after your application establishes an initial connection.
Because that first connection does not carry trace information, re-use
of it is never tracked. Consequently the application cannot accurately
match trace information to connection use.
Set trace for the
previously mentioned JDBC drivers through data source custom properties.
For example, use the spyAttributes custom property to enable JDBC
trace for the DataDirect Connect for JDBC driver. Consult your driver
documentation for details on the custom property that enables trace
for your JDBC implementation.
Additional resources
If the JDBC tracing
service cannot help you isolate and fix your problem, consult the IBM® Support
web site for WebSphere® Application Server. Use the site
search function to find current information on known problems and
their resolutions. Locating the right troubleshooting tip can save
time that you might otherwise spend on opening and tracking a PMR.