|
Problem(Abstract) |
When enabling the WebSphere® Application Server trace
component, WAS.database (for example: "WAS.database=all=enabled"), the
following message appears in the SystemOut.log:
DSRA7008I: Oracle JDBC logging is enabled, Oracle9i requires the use of
classes12_g.zip |
|
|
|
Cause |
The WAS.database trace uses the Oracle® JDBC™ Trace
Facility, which requires the debug version of the Oracle JDBC driver.
Documentation from Oracle
"What is the Oracle JDBC Trace Facility?
The JDBC Trace Facility is a runtime debugging aid built into Oracle
JDBC. When enabled, it prints messages about the execution of the Oracle
JDBC driver. Typically these messages include method entry, parameter
values, significant internal state, internal errors, method exit, and
return values.
As of 10.1.0, the Oracle Trace Facility is only supported in
classes12_g.jar and classes12dms_g.jar. All Oracle JDBC drivers supporting
JDK 1.4 and later use the built in trace facility in java.util.logging.
See the section on java.util.logging for info on how to get trace info
from ojdbc14_g.jar and ojdbc14dms_g.jar.
If you are having difficulty with your JDBC application, you might find
the trace helpful. Most of the messages are about internal JDBC methods
and so may be obscure. Still, you might get some help. I would suggest
setting the trace volume to 1 to begin with.
If you think there is a bug in JDBC, the trace might help us in
supporting you. In this case leave the trace volume at the default.
Because of the large output this produces, you will need to either trace a
small test case, or just trace a limited part of a larger application. Be
sure and include the appropriate code prior to the failure.
How do I turn on the trace?
In order to use the JDBC Trace Facility, you must use a debug jar file:
classes12_g.jar or classes12dms_g.jar. If you attempt to use the trace
while using one of the other jar or zip files, you will get either an
error message or no output at all.
There are two ways to control the trace: programmatically or via
properties. The programmatic api allows you to enable or disable the trace
and change other properties while your application is executing. Given the
often high volume of trace data, it is often a good idea to only enable
the trace for particularly suspect bits of code. If it is not easy to
change the application source, you can control the trace via properties.
These properties are read once at application startup and are not read
again. You can use both the properties and the api at the same time. The
properties set the initial state and the api modifies that state." |
|
|
Resolving the
problem |
Use the corresponding "*_g.zip" for the JDBC
driver. For example, if you use classes12.zip for your Oracle
JDBC driver, use the classes12_g.zip instead of
classes12.zip when enabling WebSphere trace
"WAS.database=all=enabled". |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|