Follow these steps to enable the tracing:
- Select the data source that uses the Universal Driver from the
WebSphere administrative console.
- Click Custom Properties on the data source configuration
screen.
- Enter value -1 (TRACE_ALL) for the traceLevel property. This is
recommended for most problem determination because it generates the
maximum amount of trace data. If only specific trace data is needed, it is
possible to enable only certain types of tracing.
Here are the values to enter for the traceLevel property, based on the
type of trace data that is needed:
Trace Level Desired |
traceLevel Property |
TRACE_NONE |
0 |
TRACE_CONNECTION_CALLS |
1 |
TRACE_STATEMENT_CALLS |
2 |
TRACE_RESULT_SET_CALLS |
4 |
TRACE_DRIVER_CONFIGURATION |
16 |
TRACE_CONNECTS |
32 |
TRACE_DRDA_FLOWS |
64 |
TRACE_RESULT_SET_META_DATA |
128 |
TRACE_PARAMETER_META_DATA |
256 |
TRACE_DIAGNOSTICS |
512 |
TRACE_SQLJ |
1024 |
TRACE_ALL |
-1 |
4. Enter a fully-qualified directory and file name for the trace output
for the traceFile property; for example, C:\DB2\jcctrace.log
5. Save the configuration. There is no need to restart the Application
Server. The tracing begins the next time the data source is used.
6. The resulting trace file can be analyzed to determine the cause of
the problem after reproducing the problem.
|